Messages

Menion, could you add an expert setting to enable long-press on theme-button to directly jump to theme's StyleMenu for quick access, so overriding theme-selection dialog?

A variant of this option (expert setting) could be, normal click jumps to theme's stylemenu - to change settings of active theme (enable routes, trails etc., change style), and long-click to open themes-selection menu - to switch to another theme, which might be less often.

With expert setting enabled the icon might appear in e.g. neon-pink colour

beta 4.15.2.4

1. is initialization during start different? Now loading instead of detailed list, though it was always quite fast

Backup manager
2. content, left to select-button: IMHO text is of no value. Honestly a shortened enumeration missing details instead of a list never makes sense to me. I suggest using a list, maybe in smaller font size if used screen-space is a matter. I suggest to begin with summary like:
Full Backup: NO
Enabled items: 9/10
item1
item2
(item3 not listed as being disabled)
item4
...
...

Just an idea.

3. status & details during processing missing. Any processing >1s should provide details about what's going on.

4. I am with Tapio, wording: "loading" during a saving-action is not the best choice

5. Congrats! (just sharing my impressions)

Most recent OAM Germany map vs. LM4 beta - anyone else?

I downloaded Germany-North 04.04.2023 today, zip, v5, and it's working fine with Elevate and with newer LoMaps-MF-beta-theme and VoluntaryUK-MF-beta-theme.
Haven't checked any map-feature though. Citynames and name-priority are somewhat different between themes.
All these different numbers are irritating, V4 here,V5 there, I suggest to call the new beta-themes simply MF-themes, as not being Locus-specific.

Noch ein Beispiel 3 km weiter westlich im Schlosspark Marquardt (Screenshot 4):

Strecke mit Navigationsanweisungen, diese sind als kleine blaue Punkte sichtbar. Es geht zunächst geradeaus, dann gut 90° nach rechts, gleich danach wieder nach links.

Die erste Anweisung sagt ungenau ,,Halte dich rechts", obwohl ,,Biege rechts ab" richtig wäre.
Anschließend biegt die Strecke links ab. Es wird aber keine Navigationsanweisung erstellt, was blöd ist.

Erstelle ich die Stecke ohne Navigationsanweisungen und navigiere dann, werden anhand der Geometrie wieder richtige und vollständige Anweisungen erstellt:

Die erste Anweisung sagt richtig ,,Biege rechts ab".
Gleich danach erfolgt die nächste Anweisung und sagt korrekt: ,,Biege links ab". (Screenshot 5).

Jetzt sag mir, was besser ist.

Das kenne ich.
Ich habe eine Strecke mit Anweisungen/Abbiegehinweisen erstellen lassen, bin dann die Strecke mit Fahrrad Vollgas und Kopfhörer auf abgefahren und habe mir die Hinweise ansagen lassen.
Manchmal fehlte mir ein Hinweis, hätte mir einen gewünscht, und wenn die Strecke kurzzeitig komplizierter war, mehrere aufeinanderfolgende kurze Abschnitte und Richtungsänderungen, besonders rechts-links/links-rechts-Kombos, wurde als Ersatz 'bitte rechts halten' zb. generiert, was zwar stimmt wenn man sich die Strecke aus der Vogelperspektive anschaut, aber nicht down on earth vor Ort hilft bildete auf jeden Fall die Komplexität der Strecke nicht ab.

War nicht optimal, definitiv nichts für turbo-speed, und hängt vielleicht vom Profil ab, habe es jetzt einige Monate schon nicht mehr genutzt.

I currently use:

xml editing per Notepad++.

a quick and easy wireless-transfer to smartphone can be realised via syncthing.
I use Catfriend1's releases on Android https://github.com/Catfriend1/syncthing-android and on Windows https://github.com/canton7/SyncTrayzor for any of my transfers.
After connecting the relevant folders (e.g. share Locus/mapsVector/_themes/XYZ_Theme on syncthing-android and accept on syncthing-windows, then point to your local XYZ_Theme-dev-sync-folder) both get synced. Synchting typically watches for changes, you don't need to interact, you can also set intervalls individually though not needed. Better work with a dedicated folder and have your xml backed up for the intial setup, though conflicts typically gets prompted.

Edit and save xml in Notepad++, the change gets automatically detected and syncing is triggered within 1-5 seconds, or manually trigger by hitting 'rescan' in SyncTrayzor if you need your 1s.
Then simply rechoose your theme in Locus, voila

seems like text-parsing of gpx-import isn't fully working
similar to this behaviour https://forum.locusmap.eu/index.php?topic=5065.0
maybe Tapio's result is also due to this?

Recognised this with 4.14.2.4 or .3, but was not able to compare this to past releases as it was with any vector-map and theme.

my ideas, personal preferences:


• LoPoints UI
optimize layout and appearance, intents + contrast / cards-style, eye-symbols (like points and tracks), sorting (allow manual repositioning and maybe some half-smart-approach based on number of usage, maybe switchable and/or combined), categories (e.g. I potentially only need the 5 ski-sport-POI-groups during winter), the whole UI-experience

• expert setting: theme-panel (layers)
available with 1-click at symbol > Map-screen content > theme. Current Map-themes (list, overview) then by using long-press at symbol.

• Backup
like you noted sure, as being basic and essential

• combined search through settings + features
like search triggers both current searches and combines the results, different symbols and maybe collapsible groups

Optimizations. Honestly I am very happy Locus is already super evolved and powerful. Really like the new and upcoming changes towards MapsForge and themes.

maybe we need backup-presets.. just need to drop this joke

(sure, backup 'settings only' should to be closer to 'full' but without \data\database as some configurations are missing)

do you use OAM ? I also had double points because OAM also places the points database in the automatic DL. You get then LoPoi and OAM Poi displayed. OAM Poi but unfortunately you can not hide. It goes only with database delete. But you have to do that again with every update.
Here the user interface would have to be extended to be able to show and hide OAM Poi.

Oh yes, I do.
But each .map.db-combo in its folder.
OAM-Germany_north
.map
.db
LoMap-MF4
.map
.db

I assume 'points around' and eye-symbol are controlling taken db and visibility differently.

Honestly, I don't use LoPoints as the whole UI-experience gives me more stress than something of use.
But LoPoints-rework is already somewhere on 2do IIRC.

Nevertheless, using new MF4-maps and LoPoints-offline and going for 'Points around' and doing this twice seems to give me doubled results, the icons are slightly different with outline and shadow and without.

edit: doubled entries are given if additionally the eye in menu is enabled. Btw would expect to have points not shown at all if eye is disabled
edit2: might be due to other .dB available in other folders

beta 4.14.2.4

MFV4 Lomaps.
...
b) When will they be in the store?

AFAIK Menion tried to cover all reg. this in a separate thread
LoMaps + MapsForge V4
See the google-drive-link over there for available maps

- chosed 1 of the linked LoMaps and copied .osm.map to a dedicated folder inside mapsVector, skipped the poi.db
- offline-theme #4: put theme.xml and the 3 icon-folders to a separate directory and zipped it (compression none, store). Put this zip into mapsVector/_themes/

everything buttersmooth using new LoMap with this MF-theme and also with any other installed theme, no delays, theme-layers and switches all like expected

installed latest beta 4.14.2.3
all fine and smooth
I am using AFA with maps and themes at
(internal)sdcard/Locus/
So far only OAM-vector with Elevate-theme, voluntaryUK-theme and activeRT5, and some Mobac-rasters, so quite simple setup

no doubled entries btw

plan is to checkout situation with Lomaps and MF-theme next

It's your choice to buy a phone with an immature screen technology, it's not Locus' fault.

I remember joeloc's request and remember me thinking 'that's valid point and an useful enhancement, well known downside of static high-contrast pixel-sections'.
It's always easy if you're not (yet) affected, and as a long time Locus user and community member he just wants to communicate his dissatisfaction about this addressed potential issue, which is understandable.
Permutating positions is not a difficult matter, though functionality needs to get coded, tested and maintained.