I want to try to bring the discussion together as not to keep iOS and Android separate.
The initial feedback is the Stats is heading in the right direction. However I see one large issue that we haven't covered - the Information Bar.
On the mobiles currently, if you tap on a route, you get some information at the top of the screen - distance, height gain etc. Its the same as on PC / macOS.
In many ways, I was just thinking we lose that, and replace it with the new stats bar. BUT, the Information Bar is in fact a little intelligent. It decides what to show due to what you have selected. Tap on a waypoint, it won't try to show you distance. It contrast you would set the Stats bar up to show a Distance box, then it would just show blank when a waypoint was selected.
So lets just stick with Distance for the moment.
You could select Distance in the new Stats bar. Then when you tap on a route, you would see the distance. Well that works.
But what if you are also recording a tracklog? Do we therefore tap on the tracklog to make it active? That seems to work also. Although I see the support issue here of 'I was seeing my tracklog distance and then it stopped' - yes because you tapped on a waypoint or something, and didn't re-select the tracklog being recorded!
The alternative is we have Distance (selected item), and Tracklog Distance as different items in stats, but then you will most likely need different setups for the Stats displays.
We can easily list
Tracklog Current Segment Distance
Very easy to define these, but accessing them through the Stats window feels a bit awkward if you want to keep looking at different information - although that would fill out the full panel view mode of stats.
Other alternatives are to move the Information Bar information above the buttons at the bottom, and like the PC, make it transient. i.e. you select something, it becomes visible, and then goes, and make this an option in Settings.
At the moment, I'm thinking to have
Tracklog Current Segment Distance
At times Distance will be the same as Tracklog Distance, but at least there is no ambiguity of what is selected.
My experience with other navigation software is that distance travelled is always available, not necessarily always visible, without having to tap on the track. That would solve the problem of tapping on "the wrong thing". I wonder if the "intelligent" information bar is trying to be a bit too clever?
@Peter - very possibly, although its worked nicely on the desktops, but then desktops aren't mobiles!
One more thought - OMNC - everything in the stats bar was either derived from the Phone itself (things like time), the GPS (current position, speed), or statistics from the recording tracklog (Distance, average speed). At NO point did the stats bar access anything to do with other GPX information. Possibly we should just keep that distinction. Stats for items on the GPX can be got in the info screens in the GE, and CURRENTLY using the Information Bar.
I'm a bit confused on this Graham. Distance to me is the distance you have traveled so far whilst walking. This is quite different from the length of a route you have plotted or a track you have previously walked. If I understand you it seems you trying to combine both into stats which to me is confusing.
Surely the info bar gives info on a plotted route or walked track (i.e. historic, static, already done) whist the stats strip & display gives info on what you are currently doing (i.e. distance travelled, height gained, average speed etc). To my mind they are different and both are important. So retain both since they offer different sorts of information.
Currently the info bar sits over the data strip but since it is translucent and difficult to read. 2 possibilities:-
1. shift it down so it lies under the data strip then make a top margin on the full stats so no text underlies it.
2. leave it where it is but make it opaque (yellow?).
I prefer 1, 2 looks messy.
Maybe I'm missing something here and I haven't quite understood you intensions.
Hi again - maybe your last post Graham alludes to what I'm saying.
Been pondering about this one. So I have my route defined and I can view it in GE, I can see it on the map, I can set a tracklog to see where I've been.
If I use my handheld GPS(Garmin) I would have to select "Navigate" to get meaningful stats on my route. Then distance has meaning in that context, How far have I come, how far to the next waypoint. If I deviate I can always recalculate. If I want to reverse a route the handheld sorts that out too.
With omn what is distance relative to? the last time I switched on gps? the start of the route that is open in GE? what if there are a couple of routes open in ge?
So unless you have Navigate option to follow a track then the only thing you really have to use is tracklog data. So then, if I'm following a route how can you give guidance on distance/direction to next waypoint unless I tell you what I'm doing.
comments crossed, I see both you and Tony eluding to the same thing...
Sorry for the very late replies on this one.
@Dennis – I think the stats view at the top ONLY relates to the GPS information (current location, altitude) and the currently recording tracklog. Currently we only have one stat on the tracklog which is Distance, but we will add others such as ascent, descent, average speed etc.
@Paul – whilst I can see where you are going with this idea, its going to be too complex for most users, and would likely confuse more than it resolves any issues is my thinking.
@Tony – I’ve been playing with it more as well, and I’m starting to think we should move the button bottom left. Tap to open, tap to close. Tap once on the stats bar to expand/once to contract. Double tap to select as now. Keeps it all very simple.
@Steve – ‘see info’ as a long press option makes sense.
@Cliff – many thanks.
@Paul - I think I set off this conversation through my own in-decisiveness. I was thinking the information bar and stats bar were the same thing, and the clearly are not. I also think having the info bar match the desktops is correct, and stats is therefore all about the GPS and device information. I think the distinction is clear. Sometimes the code is complex, other times its quite simple, but the result ends up difficult to explain to users, or is used by so few people that we just spend a lot of time writing easy configuration code that only a handful of people use, in which case, its probably wasted development time when I know I need to get Send to GPS done on the PC!
I think the stats bar is now taking shape. The information bar I think works, but needs better/clearer formatting on mobiles.
I think we are into the tidy-up stage, before we start to add further data fields to the stats bar.