Messages

3.27: great release, as usual.

• @menion recall a recent discussion & change in 2 screens to not use auto-display keyboard? One was track export. I notice for Track Folder the keyboard is auto displayed with track name field selected, whereas it is just as likely or more likely the user may want to edit the track style.
• Locus crashed with track slope mode+Arrows #3. Not for many many months has there been a crash. There was big variation of spacing of the arrow icons along track. Some places arrows merged into solid line, other places there was much bigger (and sensible) gap. See also (related but not the same issue) http://help.locusmap.eu/topic/adjust-track-pattern-to-map-zoom-level.
  
  
• Release notes screen - tap More Info button - bad URL. Even the copyright is 2014.
  
  
• Route planner: is incorrectly using direct line at start and end of route. Behavior has changed since 3.26.2.3? I have selected Car for routing. This route is impossible and incorrect. There is no OSM way at the start/ end as drawn. I have attached v1.1 exported GPX. I'll have to use RWGPS route planner until this is fixed.
  

PS - reopened 3.27.0 which had above track displayed. Completely frozen. After a few attempts was able to hide this track. Now Locus is usable again.

@menion: 3.26.2.3: track style screen is now much more responsive on older tablet. Thanks.

5. I have settings > Maps > Points & Tracks > Tap on track=Screen. However tap on track on map briefly shows track popup before track screen. Is it now slower displaying this track screen too? When I return to map this popup is again displayed.

@menion - actually this behavior is in 3.26.2 Pro release as well, not just 3.26.2.2 beta.

[@Andrew Heard]

@Andrew Heard:
2) not sure here. I was thinking about it a lot and for me cancel/save at bottom should confirm whole style edit screen. Also from practical point of view, you usually set colors etc. and then you try set limits on this altitude or slope colors and then? You wants to return to map as fast as possible, right?[/li][/list]

@menion the user may be changing any number of style settings. I see no reason for special quick return from min/max limits screen - the pencil icon has other settings below - width/ outline/ close line. Why would you expect settings limits be the last change before return to map? To me tapping Save on limits screen is just to save min/ max settings, not to confirm all other settings.

I've for now only reduced dynamic palette from 40 to 20 colors, but I'll look at it closer. I'm anyway surprised that green is so dominant. You are coloring some faked track to achieve this? May you share it with me? Thanks

I have attached GPX thanks to @0709 - so track below is latest with 3.26.2.2, and green quite dominant:


chart:

3.26.2.2: Line/ track/ route styles general comment: from my initial testing the new functionality is a fantastic advance. Well done @Menion. I have done a comparison of certain tracks pre/ 3.26.2.2 version with 0..6% slope. Now the new color is mostly red and exactly how my body remembers how hard the cycling actually was. Bravo!

• the new track style UI is slower to respond - very slow on older tablet, a little slower on Xperia Z1 phone
• tapping Save button from new Slope or Altitude min/max screen returns to track info screen but should return to track style screen
• I suggest the new Slope screen Manual "min value" should allow minus values, at present only >= 0% is possible but I may for example want slope color palette range +/-10%
• therefore at present all -ve slope % is only blue, I guess because blue is below current min 0% value?
• I have settings > Maps > Points & Tracks > Tap on track=Screen. However tap on track on map briefly shows track popup before track screen. Is it now slower displaying this track screen too? When I return to map this popup is again displayed.

@0709 & others have done a lot of work with color palette suggestions. The current Locus palette is very dominated by green, with very uneven transition between colors. :


I really like 0709's proposed 9 color palette:

Because there is no blending of colors, or maybe just less colors, if I saw a particular color (slope %) on a map I would be confident I would know what % slope this color represents.

There is also a 15 color version, but for me, more colors with only subtle differences, means it becomes harder to tell which color represents a specific band of slope or altitude.

[@Andrew Heard]

@Andrew Heard:
same problem as with removing nogo! You reduced/removed radius and change does not cover any part of existing route => no recalculation!

@menion I understand but I don't think a typical user would expect this behavior? Add nogo --> reroute. Delete nogo (yes, not over current route) --> no change. And no way to force recalculation at present, or until some suggestion like this http://help.locusmap.eu/topic/allow-3-26-route-planner-to-recalculate-route-with-different-profile.

3.26.2.1 testing: I like the new Nogo UI but recalculation after change of Nogo radius is not always performed:

• add default 100m Nogo
• route is correctly recalculated
• change radius to 1km
• route is correctly recalculated
• change radius to 100m
• route is not recalculated, whereas should expect revert to route after Nogo added

For me, if the width is defined in metres it is too thin at low zooms while if it is defined in px it is too thick at low zooms. What I would like is a width that changes at the same rate as the width of vector map roads, which is something like 150% change for each zoom level.

@john_percy +1 nice idea, maybe a help topic for voting?

"Route planner" - planning or modifying tracks/routes for later re-use, mainly for navigation purpose.

@menion - am I wrong - it is not possible to modify an existing track with the Route planner - because the modification is always saved to a new track? As previously discussed, and suggestion here - http://help.locusmap.eu/topic/allow-3-26-route-planner-to-edit-and-save-existing-track.

I have track recording automatically start when Locus is started. If you exit when track recording is active then re-run Locus the same track recording automatically continues (for me).

[@Andrew Heard]

@Andrew Heard:
Numbers on shaping points ... if they are so small that they are almost invisible, then it is not a problem they are there right?

@menion - sort of right. Now I understand "Select an item" dialog with items like "Part <N> of route" that <N> refers to the tiny number inside the Shaping point icon. Could icon size/part # size be bumped +1 point? Even config.cfg setting? I don't mind generally bigger icons. I already have config.cfg dev_gui_main_rescale_value=1.25. Maybe icon/# can take into account dev_gui_main_rescale_value?

(I have suggsted this feature -second/ splitted screen with elevation profil and slope percentage- months ago on the wish-list/ suggestion site)

@bezel - do you have a link to your suggestion on http://help.locusmap.eu/topic? Note that Tools > Route stats > chart can be configured to display Gradient% so maybe just keep summary chart at bottom of screen simple/ clean?

@silvermapper - I should mention again, in my case, I was using offline map in airplane mode.
@menion - in my case, I was never manually zooming/ panning the map, I was cycling in Navigation mode/ Hold Map Centre=on. Problem occurred maybe once or twice a day over period of 7 days touring  four months ago, but then no further problems since that time. I don't think it was related to any change of Locus version.

I note we should adopt standard terminology "auxiliary points" instead of "track points"

Correct, as these artificial helper (fake) points in the planner screen come and go without leaving any trace. So not to be named "track points".

@0709 - as far as I know, until 3.26, we used term "track points" and no-one made mention of it. I agree Aux point is probably better, especially in context of Route Planner.

@menion - updated to Locus Pro 3.26 but crash in Route Planner when I tap on the big blue Route Profile button - "Unfortunately Locus Map has stopped" - what do we call this button so everyone here uses same language/ terminology?

It looks you have old phone. What's the Android you use?

Thanks @Bucky Kid. Well observed. 3.26.0 working fine with Sony Xperia Z1/ Android 5.0. Crashing with Samsung Note tablet/ Android 4.0.3. Tablet was working fine with the 3.25.5.5 beta.