Open Kelly-Foster opened 6 years ago
Additional insight: bug only occurs for me if I have data graphed on right side. I this test case, I put baro temp and airspeed temp on left side, and throttle on right side. Bug occurs in latest version build 1.3.6823.9561 which I upgraded to just now. Unfortunately that upgrade has introduced a new minor issue. Check out fonts in upper portion of main MP window.
Kelly
the font issue is a windows 10 update issue. with dpi scaling, and I have a feeling the other issue you are having is exactly the same issue.
Sorry, I don't fully understand your comment. By font issue, are you referring to the grainy text in the main tabs at the top of the MP window? Or some other font issue? My main concern in creating this GIT issue is the horizontal axis in graphing, where "use time" doesn't work well if data are on right axis as well as left, and flight mode labels disappear. That can't be a Windows issue because if I only graph data on left side, it is well behaved.
Kelly
this is in the compatibility tab of the MP shortcut icon
what are yours set to?
I have the same time issue. If I check "Use Time" then the entire scale is shown 00:00:00.000 and no actual time is shown.
Furthermore, "Show Point Values" shows the time oddly, in this case "30-Oct-50 00:00"
Font issue is not as apparent (Win 7) but the MP tab button text is rather small and not particularly clear
Running MP 1.3.58 build 1.3.58.0 with ArduPlane master latest (from ~Sept 4th) on Matek F405-Wing on Radian Pro. I am documenting problems I've experienced for some time with MP's handling of the horizontal axis while graphing DF logs. Atttached are six screen grabs as I do the following:
Request: when "Use Time" is checked, horizontal axis is time, displayed by hh:mm:ss.xxx, perhaps with option somewhere to change that format to integer seconds. In either case, please continue to display flight mode, messages, and errors if those boxes are checked.
Second request: (much less important than first request) please consider and optional legend that tells me which horizontal band colors correspond to which flight modes. Sometimes I am zoomed in beyond the label, and have to zoom our or pan to confirm that blue is FBWA, pink is RTL, or whatever the mapping happens to be.
I find time in hh:mm:ss.xxx to be the most useful and intuitive horizontal axis by far. I think line number is more dev-centric. Users think about "2 minutes into flight I hit RTL as a test and it started diving to the ground". I will often have a video editor open looking at recorded FPV cam + OSD while reviewing logs. Line number in DF logs means nothing in video review.
Thanks for listening Michael.
Kelly