Feature Request: Show Total Route Time on route legs.

[Stiggles]

Current ETE value on the for a route only shows the length that the current leg will take.

It would be extremely useful to show the total accumulated route time next to the leg time. Knowing the total flight time is invaluable for calculating fuel loads.

Currently, a leg of a route shows:
[DISTANCE] | [HEADING]/[RECIPROCAL]
[SPEED] | ETE [ETE LEG]

A better layout would probably be:
[SPEED] | {HEADING]/[RECIPROCAL] <- Speed and heading are the most important two values and should be first
[DISTANCE] | ETE [ETE Leg]/[ETE Total]

[ServError]

My only gripe with this is that it increases the size of the flight leg text box. I'm playing with it and will see if anything looks good, including maybe having it under each altitude indicator.

This was part of the reasoning behind the CSV export feature. Letting people do calculations in excel was a compromise to try to keep the map itself tidier.

[Stiggles]

That is a good point. What about adding the information to the Plan Summaries popup*, or (even better) in another popup that has a table with the flight plan information laid out**?

*On the Plan Summaries, it could also be sort of like Google Maps directions where on the line under the Title it has a line in a smaller font that says the Route Distance and the Total Time of the route.

** Sort of like an in-app display of what would be sent in the csv with some basic calculations for additional information, but without the user needing to use another program to view it/run the calculations. With something like that you could put in extra information in the table without cluttering up the map. (Stuff like wind, TAS, Waypoint Names, Waypoint Coordinates, Comments, Etc.)

An additional possible functionality of a table popup would be to make it editable on specific values which could be used to rapidly change aspects of a route without needing to click around the map (WP altitude and leg indicated airspeed).

(Sorry if this is technically a different, much bigger feature request.)