MP log graphing issues with time axis and mode labels

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:

1. I rectangle zoom in on data of interest using left mouse press drag release. Using all MP defaults in log viewing, specifically "Use Time" unchecked, flight modes, messages and errors all checked. Note horizontal axis is "Line Number (10^3)". Note also that I get flight mode labels and color coding on the bottom of the graph, which is highly desirable.
2. I then check the "Use Time" box. No change in graph, so I then roll middle mouse button forward one click, which zooms in on the current view. Horizontal axis changes to 00:00:00.000 and flight mode labels and color coding disappear. Dang. Not at all helpful.
3. Then I right click "Set Scale To Default". 00:00:00.000 is replaced by integer # of seconds (since boot?). Well, that's more helpful than 00:00:00.000, but flight mode labels and colors still missing. A few messages appear in the pre-flight portion, but no flight modes or messages during flight.
4. I rectangle zoom in on a region of interest, and horizontal axis is integer # of seconds, but flight modes and messages and color coding are still absent.
5. I disable Use Time, zoom around a bit, and notice duplicate flight mode labels for RTL. None of the other flight modes are "double labelled". Not sure if that's intentional or not. Not a huge issue, but thought I would point it out in case it's not intentional.
6. I zoom in on an area with lots of flight mode changes (perhaps during pre-fllight checklist) and confirm that only RTL is double-labeled.

**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


No source files or tests are named. Start in Mission Planner's log viewing graph with a DF log and reproduce the Use Time toggle, zoom, default scale, flight-mode labels, messages, errors, and duplicate RTL label behavior described in the issue. Done means time-axis formatting works as requested while enabled labels and color coding remain visible; the optional mode-color legend is a separate consideration.

Written by the indexing model from the issue text.