Quote from: Menion on Yesterday at 15:26:17Any opinions? Maybe introduce a third time?@Menion I'm happy with current method, but with any change I think there will be opinions for/ against
Quote from: Menion on Yesterday at 15:26:17@ChristianThanx. that solved the problem.
visible nav points > please check app settings > Points & Tracks > "Show navigation commands on map". Any chance you enabled by yourself accident?
Quote from: Menion on Yesterday at 15:26:17@WildWortWechsel
rec STOP button > it is always visible as an indicator that recording is running. Settings ignored by intent.
...
searching a city > not sure about the icon. There should be a better general search icon. Steps to reproduce?
...
change of the button in the right panel > it looks, based on the distance to your location, that you are somewhere really far away from your home. Center![]()
Quote from: Menion on Yesterday at 15:26:17Currently, app compute times as:
- track time - all times between trackpoints. Breaks are skipped and not computed
- track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)
What you want is to change this behaviour to
- track time - simply difference in time between the first and last point
- track time (movement) - all times between trackpoints. Breaks are skipped and not computed
Any opinions? Maybe introduce a third time?![]()
. I have to hide it correctly.
Quotebest solution is to simply ignore "comment" and use "description" only.It would be clear to everyone if only "description" is visible.