Re: [APP] - version 4.33.+ ( 03/2026 )

Started by Menion, March 04, 2026, 11:16:40

0 Members and 20 Guests are viewing this topic.

Andrew Heard

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
 
4.33.0.9-1211 GOLD user ID:c7d47597a
  •  

Joska

The complete time from start to stop should not be ignored, but maybe, I'd misunderstood that issue.
---
  •  

Žajdlík Josef

Total time on the track is important for all types of endurance sports such as trail running, long marches, cycling, triathlon, biathlon, etc. For all of them, the ranking is calculated according to the time spent on the track, including breaks. That is why applications such as Garmin, Strava or Samsung Health also show this time. But it is also important for amateurs. For example, when I want to look back at how long I walked the "Vandrácká 50" five years ago, I'm interested in the total time in order to estimate when I'll probably return home.
Therefore, I propose to unify the indicators with all sports applications:
track time - simply difference in time between the first and last point
track time (movement) - same as track time, but only when speed is above the threshold (around 2km/h)
  •  

slarti76

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'd wouldn't mind a third time or ability to change the threshold. For hiking and snowshoeing, the "movement" times are frequently too low, as in ascent, you easily get below 2km/h.
  •  

Menion

@Ulrich Kiermayr
Isn't the problem with the dashboard already solved in the latest Beta version?

@WildWortWechsel
track rec button > if you have set the "Auto-hide" option for this button, it should be visible during recording, always. Otherwise, it should be visible or hidden, based on settings.

incorrect search result icon > I understand you have your own icon set in the settings. You wrote about some problems with the search system and I ask to provide some easy-to-follow steps, so I can simulate it. Thanks



Times, thanks for the feedback. I'll have to discuss with the team next week more deeply (also because we have to changes adapt on iOS and web as well).
- Official help (ideas, questions, problems): help.locusmap.eu
- Advanced topics, sharing of knowledges: you're here!
- LM 4 Beta download, LM 4 Release download

Ulrich Kiermayr

#185
Quote from: Menion on Today at 09:09:31@Ulrich Kiermayr
Isn't the problem with the dashboard already solved in the latest Beta version?


Unfortunately no. The bubbles are gone, but the dashboard still draws over the guidance/navigation panel, intercepting clicks.

You cannot view this attachment.

LG Ulrich
  •  
    The following users thanked this post: Menion

WildWortWechsel

Quote from: Menion on Today at 09:09:31incorrect search result icon > I understand you have your own icon set in the settings. You wrote about some problems with the search system and I ask to provide some easy-to-follow steps, so I can simulate it. Thanks.


Hi Menion,

from my side it was only the icon. I removed it --> Problem solved.
  •  
    The following users thanked this post: Menion

Mick FU

About times, can't find again the post, but total_elapsed_time (from start to end including pauses) is at least computed during fit file export.
@Menion
You cannot view this attachment.
  •