Main Menu

Recent posts

#51
Locus Map / Re: [APP] - version 4.33.+ ( 0...
Last post by Menion - April 15, 2026, 09:09:31
@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).
#52
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by slarti76 - April 15, 2026, 09:00:37
Quote from: Menion on April 14, 2026, 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.
#53
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Žajdlík Josef - April 15, 2026, 08:23:10
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)
#54
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Joska - April 15, 2026, 07:48:10
The complete time from start to stop should not be ignored, but maybe, I'd misunderstood that issue.
#55
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Andrew Heard - April 14, 2026, 23:29:22
Quote from: Menion on April 14, 2026, 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
 
#56
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Christian - April 14, 2026, 23:09:39
Quote from: Menion on April 14, 2026, 15:26:17@Christian
visible nav points > please check app settings > Points & Tracks > "Show navigation commands on map". Any chance you enabled by yourself accident?
Thanx. that solved the problem.
#57
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by WildWortWechsel - April 14, 2026, 19:27:15
Quote from: Menion on April 14, 2026, 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  ;)


Hi Menion,

thank you for your answer!

In the earlier Versions the stop button did "vanish" from the screen. That's why I mentioned it.

About the icon: see the screenshot with the expert setting of the "default point icon." Isn't it the default POI Icon?

And because the side panel etc. The center button disappeared 😉

Greetings, Dieter
#58
Locus Map / Re: Re: [APP] - version 4.33.+...
Last post by Ulrich Kiermayr - April 14, 2026, 16:29:40
Quote from: Menion on April 14, 2026, 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 would expect (and am used to) the current behaviour.

If a third time is introduced, then add a "wallclock time" which is the delta between first and last point of track.

@Menion
Is it possible to do something about https://forum.locusmap.eu/index.php?msg=80839? If not, I'd have to redesign the Dashboard somehow.

Greetings, Ulrich

#59
Troubles & Questions / Re: Locus Map Gold is too dark
Last post by Wolfgang - April 14, 2026, 15:40:50
Hi,
today we have our first walk in sunshine with the new option (Brightness Limit Profile set to Light).
The display was on full brightness all the time!
Greetings Wolfgang
#60
Locus Map / Re: [APP] - version 4.33.+ ( 0...
Last post by Menion - April 14, 2026, 15:26:17
@Andrew Heard
slope chart > I've increased the strength of the filter, so it should better match what you see on the web.

zoom with respect of the current selection > done

Smooth movement > yeah, I know. It still needs more time and testing on my side.

Online search problem > it was completely rewrote in last few days so give a try to the next app version, thanks.

@michaelbechtold
2 vs 4 charts > check please menu in the "Charts screen" > Settings > Display all charts

@Tapio
slow loading when a huge number of photos is on the device > same experience on own device. Will look at it

@WildWortWechsel
rec STOP button > it is always visible as an indicator that recording is running. Settings ignored by intent

missing translations in theme > ah, nice. Fixed

update of maps > there is something not working correctly when dealing with maps manually (or restoring some backups etc). I know, but it needs a lot bigger update under the hood. Check for updates should work correctly for maps updated directly on the device over the app.

Crashes at start > hmm, hard to say what may be the problem. Anyway, please wait for the next 4.33.0.10 version at the end of this week. I'll do a lot of fine-tuning this week. Thanks!

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  ;)

elevation chart zooming > I'll look at it. And performance - yes I know, not ideal mainly for longer tracks. It will improve itself over time I believe (as the Vico "chart library" will be improved)

Beta map manager > yes, I know. Forget on it for now  :D. I have to hide it correctly.

@Blihi
problem with times > steps I can follow to simulate this problem? Thanks

@Christian
visible nav points > please check app settings > Points & Tracks > "Show navigation commands on map". Any chance you enabled by yourself accident?

@Diddi
gc icon pack > hmm, good point, improved. Thanks.

@TrulloF
nice try!! I've never used this API in production so we will have to fine-tune this a little.

I've moved your post here: https://forum.locusmap.eu/index.php?topic=9593.0 and will look at it during the week.

@Žajdlík Josef
This is more complicated and on discussion with everyone.

Currently, 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?  :)