I have never used the display of a line with a multicolored version. However, I would greatly appreciate if Locus had this feature in a simplified way in the route planner. This could be an option in the Scheduler menu: "Notify X-Percent Tilt". When I activate it, I would set the percentage and Locus would need a reddish part of the track with this slope. This could be used for planning a trip for rides with children, etc.

Currentlya) it is possible to setup width of lines in Route planner, nothing moreb) global line style affect these lines, weirdI was thinking about it, and in the end, I've removed option to set width of line and instead, I've added into menu option to setup full style of lines, thanks

@john_percy:2. when you tap on "Line coloring" selection, bottom panel completely disappear??3. it worked in same way also in previous versions, maybe it was not so visible as is not. Point here is to highlight track and it's orientation, as much as possible. Maybe little confusing when we consider that symbols are disabled, on second side, it should allow to see line better. Hmm should be more logical to just highlight such selected tracks always with simple arrow and inverse base color? Maybe it worked like this in previous versions and not how I made it now. Thanks

2. The second and third images show how the bottom button panel appears and the Cancel and Save buttons disappear when either of the drop-down menus are selected

3. Current beta:I hadn't noticed this behaviour before but checking on the current full Pro version with a simple line, the track's colour inverts and arrows appear in the colour of the non-inverted track. I don't see why arrows should appear at all if they are not selected.

Ah this one again.Stupid unsolvable "bug" in Android: https://issuetracker.google.com/issues/36992828 . Well, Android developers consider this as "not a bug", so it won't be solved and as I'm searching, still no one discovered any hack how to bypass this, sorry.

Ah this one again.Stupid unsolvable "bug" in Android: https://issuetracker.google.com/issues/36992828 . Well, Android developers consider this as "not a bug", so it won't be solved and as I'm searching, still no one discovered any hack how to bypass this, sorry.

I understand. The particular problem in this screen is that the Save button disappears, making the UI useless.

Hi Menion,seeing dp, px mentioned, this reminds me of a long standing pain: Locus is no longer reasonably compatible with Mapsforge. And the themes are just the prime example: size definitions differ, missing priorities and alike.I think this house-keeping is long overdue. And this is not a question of voting, just to close that door.Also the extra label layer like in Cruiser is the only way to get in control of the currently totally unreliable and unpredictable displaying of labels.Christmas is nearing - time of a gift :-)TXs and cheersMichael

Hmm currently in Locus Map is available MapsForge in version 0.8.0, which is automatically used in case, generated map is in version 4 and higher. So if you are able to generate maps in this version, feel free to test and use it.

I know this and tried, but there are other issues.The MF libs alone will not give you the proper label layer, there is more algorithm needed, which would benefit Locus itself as well.The parallel existence of Locus private and MF algorithms do not deliver the strengths of MF into Locus. In fact the discussion is about COMBINING the strengths of both. Long overdue ...

Mapsforge is a powerful set of APIs, but not a complete App in itself.The proper label display feature is built into the Cruiser App (using MF libs), but is not a gift from those APIs automatically.You can test by displaying a heavily populated area with Cruiser and compare it to Locus with MF-ML maps (from MF or OAM/elevate theme), which enfore the MF lib you integrated. You will be shocked by the difference.Rendering has two modes, and both show much a better selection of Labels. "Priorities" in themes make a big positive difference already, compared to Locus. And the extra Label Layer shows a fully proper and complete set of labels, as dictated by the map content and the theme.If you look at a map and cannot tell if a blank space is because there is nothing of what you are looking for, or if the App has "forgotten" to display the expected - not good ... !

Michael thanks for an answer, but you did not answered to my question I think. Or you wants to say that even a map in version 4, thank in Locus should use latest 0.8.0 version of MF library, looks different compare to other apps that use this new version of MF?

True, Locus display via MF 0.8 looks different from Cruiser, which is kind of reference App for MF.I documented with two screenshots, both with the basic OSMARENDER theme:- the Cruiser one (advanced, lextra label layer mode) correctly shows both cities- the Locus one is missing WiesbadenWhen I check Cruiser in normal mode, it is missing Mainz instead.Rendering without Label Layer is like rolling the dice ...Maybe you have a talk with Emux to explore.

BTW: a full migration of all MF features may be a longer term endeavor (while preserving the speed of Locus :-).But I suppose that theme functions like "display=always" will not be too hard to implement. And would give a LOT of power to theme authors.Priorities would be the next on the list, but may need some more thoughts.TXs and cheersMichaelPS: it's great to to attach bells and whistles, and fancy little towers and more to a house, but from time to time it's key to upgrade the foundation :-)