Messages

I suggest to not show only the header of search results and the map, but to also show part of the list, maybe 3 most top items and additionally indicate that this is a scrollable list.
When I slide the header it can only be slided fully to top, no mid position, and I don't see part of the map but the full list, well.

As suggested, see GMaps, heavily optimised and developed over the years. You see the map, you see the results, map height is mostly kept so no disturbing/irritating changes, results list is horizontal and neighbouring results can partly be seen so you understand that there is more, very screenspace friendly, you have categories, 'search this area' is genius to check left and right and trigger new search on demand, but in Locus we now have it automated which also is a new experience, et cetera et cetera. Nothing more to say and worth some inspiration.

As a physicist I honestly don't understand the logic to show results not requested by user's input and specified search but flooding the map, I will need an option to disable this speciality.

woah, that's a rough start..

LM4 beta 4.16.0.2 1st flavour tested, try&cry
LM4 beta 4.16.0.3

as polishing is needed and to save myself I will drop a note only at time
- cursor in search input: I have the keyboard, but the 3 basic android control-buttons are missing
- if I search by category, eg. health, also results of other categories are additionally shown on map
- if I input letters the shown results are located somewhere else, not nearby current map cursor, and also no distance is shown in the list.  As I don't see the results in context of a map (location) it is of limited value
- if the results are shown around the map as icons and I click the map for 1-2 seconds the results are gone. Might be by design, don't know. If I reenter search there is a bin icon next to category though nothing is actively shown
- the result list seems to be a mixture (as noted in #1) with missing visible structure. So I am first busy to get the clou, structure or filter the results, then I can profit of them..this should already be given by a proper design & layout

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.

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)

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

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.

At the forum mainpage https://forum.locusmap.eu/index.php I see a block with recent posts at the very bottom

using 4.11 as of today

I suggest to pause latest brainstorming on presets for some releases and updated features, until new calls possible, probably Menion and team save existing links, ideas and comments to some MS OneNote or alike. BR

plannings for introducing custom buttons in dashboards would improve flexibility and if so, I am with tapio, it should be possible to trigger any kind of action with it, like any other digital (UI) or hardware button would do.

@Menion: when optimizations in LoPoints and search get addressed, I suggest to also use some 2 weeks of collecting/sharing ideas, opinions, needs upfront

- cannot really see a change
- do the buttons have a 1px border of different color? Looks a bit strange, some visual effect
- compass needle - this way ok to me
- blue color of lock-symbol for centering-lock is still of low contrast and super ugly

LoPoints-experience and the partially illogical logic noted on page 3 https://forum.locusmap.eu/index.php?topic=7496.30#lastPost and month ago.
Must be more confusing for people not that experienced with LM though.

MIUI offers the option of hiding the navigation bar for certain apps. But Locus does not react to this setting.

I suggest to not use those specialties as this might bring nightmares to Menion to deal with all those gimmicks with potential misbehaviours, cornercases, whatever..

[@Andrew Heard]

@Andrew Heard
Both "itineraries" have different use-case. In the route planner, it is mainly about the option to see all segments on one screen and the option to change easily it's order. In the active navigation route planner, it is about a common itinerary known from bigger navigation apps. It should be read-only and give quick overview of what will come.
Can't imagine how to merge them to be true 

I guess Andrew meant:
- RoutePlanner-iternary being an parameter-list (input, via-points)
- Navigation-iternary being an calculated result-list (output)(containing the via-points as used constraints)
Currently you see the (calculated) results in
- RoutePlanner as drawn route > graphics only
- after starting navigation as route & iternary > graphics + table
even though it's in both situation already calculated.
In RoutePlanner maybe without fetching road-names.
With having the full result you can better decide whether to use it or not..if you started the process of navigation, it's not that easy to step back.
Maybe you are in unknown territory and someone gives you some hints, use a certain  street, whatever..

Currently you have to do some clicks and cannot go back and forth easily.

In my opinion the iternary could gain some structure and styling to clearly differ between input-points and calculated parts between
- shaping point 1
-  road/segment 1
-  road/segment 2
- ..
- shaping point 2
-  road/segment 1
- ...
- shaping point 3

maybe collapsable