Messages

Same like Tapio, though I have the top panel-visibility mostly set to 'auto-hide' to have the fullscreen-experience. I could also live with that. But it lacks beauty.

Full-screen setting > I'll discuss this with my colleague, but this setting will probably be removed. It is a hack that no longer works correctly.

'Hack' might be a strong word. There a quite a lot of apps out there with fullscreen-modes and touch-overlays, probably technicallywise it's more a matter of stack-concept, parameters and drawing, guess so.
Will bottom panel change in the feature? it is working perfectly there..

[@T-mo]

@T-mo
select track > Re-route > what track are you "re-routing"? Recorded or previously planned? I've tried it and it works as expected to me.
attention info > app asks if you want to overwrite, so it is ok, isn't it?

- recorded track. I found the issue. I choosed Re-route, planner opens and the correct profile was preselected. I checked, preselection was fine, nothing to do. As there is no re-calculate all any more in burger-style-menu, I thought job done, save as new track.
But a closer look tells you, all track-parts are with pencil-symbol, not bike-symbol, and probably not recalculated at all. You have to actively trigger recalculation, which can easily done by selecting the already selected profile. Dont trust your eyes or logic. Honestly that's easy to miss.
- why do you want to overwrite a recorded track with an artificial one? Re-route means re-use to me, but not re-write. I guess in 90% of use-cases it will be meant to be used as starting-point without the intention to get loose of recorded data. Maybe you have same start and end and want to have a training-, sightseeing- or explorer-variation or you want to drive patially similar with extensions or whatever. From my point of view.. Question is, if everyone assumes at dialog 'Save track' means overwriting your once recorded track.

[beta]

Klingt frustriert und nicht mäßig konstruktiv.
Du nutzt LM 4.31.3.6 beta, das musst Du ja nicht machen wenn es stabil bleiben soll. Mehrere Libraries wurden aktualisiert. Zudem kannst Du das ja im beta-thread mitteilen, 2 Sätze und Bilder genügen.

Ich selbst nutze die LoMaps nicht.
Siehe Bilder,
LM 4.31.3.6 beta, internal theme
LoMaps D-NRW Sept.2025

Entspricht jetzt nicht meinem Geschmack, aber funktioniert grundsätzlich. Vermutlich werden das mehrere benutzen. Ob das jetzt so aussieht wie es muss müssen andere beurteilen.

Lieber Holger,
ist etwas nichtssagend.
Tu mal Butter bei die Fische,
welche map, welches Theme. Einstellungen dazu korrigiert bzw. Theme nochmal neu ausgewählt, dauert ja nur 2 Sek.?
Und wie passt das zum Thema, auch nochmal eben ergänzen bitte.

@Mick Fu
seems to be controlled elsewhere, maybe hardcoded and at least to depend on set App language.
I suggest to open a dedicated topic.

bugs:
LM beta 4.31.3.6

• App language not saved, always defaults to system language at start.
• select track > Re-route > profile with 'Include navigation commands' and eg. 6 shaping Points > save as new track. Select New track > Tools > internary. Locus tells 'track includes no waypoints', which could be at least the used shaping points, and no navigation commands are given. I have to use 'Make a copy' and enable 'Add navigation commands' to finally achieve navigation commands.
• attention: ditto, Re-route. Then using the save button (icon next to burger-menu) a dialog opens to overwrite the current track. This might be the original one used for Re-route. Quite dangerous. IMHO a Re-route-track should be handled as new track, derived from the original track, and save should be the same like 'save as new'

@Mick Fu
check folder
Locus/data/tts
there should be a tts-file, fr.tts in your case which can be modified
Files are also available at https://github.com/asamm/locus-map-tts-commands/tree/master/src/main/assets/tts_commands if you missed to keep a backup.
Not sure, IIRC it's also mentioned somewhere in help.

Menion hatte die Center-Button-Funktionalität erweitert und das ist auch sehr gut geworden, ist aber leider noch nicht ganz fehlerfrei.

Der Button scheint durchzucyclen, aber der erfasste Status passt nicht immer.
Da ist irgendwo bei If-Then- oder Case-Abfragen noch ein Wurm drin oder eine Variable wird nicht immer richtig gesetzt. In der Folge funktioniert auch die Ausrichtung nicht so wie gedacht.

In der aktuellen LM4-beta ist das auch noch so, siehe folgende Beschreibung von mir, bug derzeit weiterhin vorhanden:
https://forum.locusmap.eu/index.php?topic=9260.0 #5

Meinem Verständnis nach muss die Button-Mitte leer sein, wenn das Fadenkreuz nicht auf der aktuellen Position ist, und wenn auf der aktuellen Position dann mit weißem Punkt.

Es wäre gut bei Fehlern auch seine Locus-Version zu nennen, geht's um das noch mitgepflegte Locus-classic oder um das aktuellere LM4.

Actually it's not masterclass to make an app featurerich but simple in appearance and use.
Though you will easily find bad design or control solutions.
Look at the android-dark-material-design, where active controls or tabs in browser are with that darkgrey that it is pita to reliably distinguish from black. Assuming there might have been a LOT of meetings and finetunings to bring that android-design to life.

Well, that red sign next to position is the worst decision of 2025.
Everything else is said.

I guess Locus will never be for beginners. E.g. look at the simple satellite radar screen with GPS off and you're immediately out of the game, 'no visible sattelites'. Don't get in panic and touch the screen..
I'm fine and understand the logic

[@Gerhard57]

@Gerhard57
duplicate categories > hmm, good point. It is because of change in the language. Give a try next version please.

Problem still exists in 4.30.1
Change of language was just a try to see if it's a problem of translation.

How can I reset the list of categories?
I am using only online LoPoints with OAM maps.

It's the same with english language, see pic, and it's by design, it's actually there since several versions incl. new LoPoint-playground.

[@T-mo]

reg. https://forum.locusmap.eu/index.php?topic=9260.msg79024#msg79024

@T-mo
New LoPoints > I believe the profit of the change is quite big. No difference in online/offline work. A lot richer content of POIs, full compatibility of offline and online, better placement on the map and for use - very easy to modify both worlds at once.

Db documentation and support for 3rd parties > no, not planned and definitely not recommended. New system is a lot more complicated than the previous and we need to keep compatibility with the online and iOS world. That's why "Other POIs" will exist and will still be well supported.

well it's a db and therefore not more complicated as it is by itself.

No doubt it makes sense to unite online and offline if different and grown structures have been in use.
It also makes sense to use a consistent structure if data of different sources get used, parsed, loaded, combined, and processed, and shown in a consistent way. If the community and userbase will bring additional content, like e.g. it is with Komoot, the more important this is, sure.

Well, noone expects a full db-documentation, plain information can be dropped at a dedicated github-page without big efforts as you know.
Even the same GUI-part, category-filter, mechanism could generally be used, though be separated to distinguish and better identify problems due to external database-files (offline), just in case. And back-loading of those can also generally be disabled to never bring those online, if building a LM-driven database is the goal.

I personally tried the old but now preserved LoPoint-part from time to time but decided not to use it consistently as it never was a satisfying experience, category ui in early design-state, poi loading awkward, search pois puh.., poi difficult to distinguish from the background, too small size and too small frame and no features like temporary switch map to bw, etc. It was a start.


Well, I suggest to rethink your view and to support with informations about the changed db-structure, consider 3rd-party sources like e.g. OAM, in my opinion this might better preserve community support and bring a better and more satisfying Locus-experience at all.

Hmmm, I guess the new LoPoint needs some basic love.

see pics, made with 4.29.0.14, but still same with 4.30.0

• only new LoPoint enabled, only 1 category 'food & drink'. AFAIK those are online.
• beside the enabled category also a bunch of other poi-symbols get shown/drawn. They are without the rectanglular-icon-style, but old-school-style.
• if I select one of those it gets the rectangular-style for the time of selection
• ANY selected poi does not get highlighted in any way, maybe orange or neon-green rectangular frame, bigger size, only its item-details pop up
• selecting and switching between those additional (not enabled) poi takes some time, maybe 6 seconds, until the map-drawing gets updated, basic item-details are shown instantly. Maybe it's due some online-loading, parsing, checking for picture, whatever

However, I would appreciate it if this track info panel could be individually configurable. Unfortunately, this is not planned for the time being.

My choosen long track title results in 3 lines, this of course consumes a lot screen space. But the rest is not collapsable and the map size is still fixed and finally limited.
IMHO the applied size is too small.

"point, red marker"
Check the Expert Settings to see if "Centre on point" is enabled under points.

I disabled this setting as it can be annoying while checking different poi in a close area and poi can already be seen though not centered (so centering is more confusing than it helps), also search results in focus and then automatic map centering, and potentially loosing focus in situations not desired.
Enabling the setting activates the desired focus, centering map, sure.
IMHO pressing the dedicated UI-element (icon with indicator of off-screen-position) should also provide this functionality if actively pressed, my suggestion, currently it does nothing.

pt. 2

[New LoPoint]

MapGooglePlayAfa_4.29.0.11_1179_beta

see pictures

• track overview - shown map only uses a small amount of screen,  a lot of area is used and wasted with information not that relevant to me
• point, red marker - no action when clicking on it, centering to point not working
• LoPoints. When enabled also other symbols are shown. I guess their of 'other poi', though them are disabled in this menu

New LoPoint
Well, though it makes sense to optimize data generation, workflow and handling to optimize resources, the profit for the user is more or less low.
The GUI enhancements are a good start and a general rework was on the list for at least 1.5 years, maybe more, IIRC.

My concern is mostly data usability.
From my point of view the strength of Locus has always been community awareness and community support and the potential of integrating data of other community or enthusiast projects and open or free available sources like OAM, brouter, Sonny's DTM, themes etc.

As far as I remember the offline POIs had a huge community interest and some individuals managed it to reverse-engineer the used db-structure IIRC, with huge efforts, maybe it was also delivered at some strongly progressed point.

Will the new used db-structure be documentated and released to also be used by the Locus-community, to also integrate other POI-sources, adapted OAM-data or other future projects?

Hello,

I've discovered a problem with the route planner.
When I create and save a route, my route is saved with the date 1970-01-01T and the time 00:00Z, see attachment.
...
I don't know which version this is from. I just noticed today that I exported a GPX file and another app displayed it with the date 01/01/1970.

Mystical 1970-date.
Just search the forum for 1970
I temporarily struggled with it with LM 4.28 and some older db-entries.

I guess it's hardcoded somewhere in Locus-code and used as fallback-date by Menion at some function-calls. Or whatever. Obviously it also seems to be used for those waypoints-time-stamps during generation.

Yes, no-one needs those 1970-dates. Though it indicates some lack and outdated handling