[APP] - version 3.27.+ ( 8. 11. 2017 )

[menion]

Important links
- blog post about major version
- list of news of public versions

Versions
8. 11. 2017 - Locus 3.27.0
12. 11. 2017 - Locus 3.27.1
21. 11. 2017 - Locus 3.27.1.2 - BETA version
26. 11. 2017 - Locus 3.27.1.4 - BETA version
28. 11. 2017 - Locus 3.27.1.5 - BETA version
4. 12. 2017 - Locus 3.27.1.6 - BETA version
8. 12. 2017 - Locus 3.27.1.7 - BETA version
15. 12. 2017 - Locus 3.27.1.8 - BETA version

[Andrew Heard]

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.

[slarti76]

Serious bug in 3.27: Cannot save track descriptions
http://help.locusmap.eu/topic/cannot-save-track-description

[Bucky Kid]

I appreciate the new track style editor, but can not figure out how to make the pattern transparent to map (as on old version). Was this combination left out? I observe when using a track pattern, as zooming out the pattern prevails more and more over the track colour, but maybe it's a question of habit.

Serious bug in 3.27: Cannot save track descriptions
http://help.locusmap.eu/topic/cannot-save-track-description

I can change track description.

[menion]

@Andrew Heard:
Unbelievable precise notes as usually, thanks
1. best should be to measure reasons why users usually open this screen, ah ... later (measuring). So, changed.
2. "crashed"? Like real force close of app? Then I'll need a log. Otherwise as I mentioned in help desk topic > improved.
3. nice thanks. In this case, rarely issue on Michal side, nevermind, post about version also appear in notification center, so who wants it, find it.
4. this is caused by very old problem in BRouter ( expect that other sources do not have this problem, right?), that I've fixed by this ugly hack. Should be improved, agree ...

@slarti76:
fixed as mentioned in help desk topic, thanks

@Bucky Kid:
What means transparent pattern?Transparent color is not correctly applied? About "too much symbols at low zoom level" ... read Andrew's point 2

[tapio]

My Locus crashes now when I add POIs from the poidb, no matter which category they are from. It happens when I tap inside a category, eg. "Museum". Germany North map+db from the store.

Anyone else?

[Bucky Kid]

What means transparent pattern?Transparent color is not correctly applied? About "too much symbols at low zoom level" ... read Andrew's point 2

Hello menion, I meant if the track line can be transparent in places where it's cut off by the pattern, e.g. dotted line will alternate the track paint colour with the map under the line. In versions 3.26- it worked so. Pattern transparency in 3.26.2 vs. 3.27.0:



As for zooming out issue-got it.

[Andrew Heard]

@Andrew Heard:
2. "crashed"? Like real force close of app? Then I'll need a log. Otherwise as I mentioned in help desk topic > improved.

Map screen freezes. Very repeatable - display track on map, tap on track, return to map, repeat a few times. Android says Locus Map is not responding etc. I have emailed log direct (15MB). Attached is GPX. It seems related to the manual slope track style. I have never seen this before, even in last beta.

@Andrew Heard:
4. this is caused by very old problem in BRouter ( expect that other sources do not have this problem, right?), that I've fixed by this ugly hack. Should be improved, agree ...

I hadn't seen a direct line at start and end of track.

[menion]

@tapio:
thanks, next version

@Bucky Kid:
Hmm wait please on next version. If I understand correctly, this should be solved.

@Andrew Heard:
hmm thanks. No useful in logs, but I think I was able to simulate this problem. Not sure why this happen, but one small change seems to fixed it, so next version as well ... (probably tomorrow).

[tapio]

Is the track renaming bug fixed? I cannot rename an existing track, no matter if displayed or not. After all, it keeps its old name.

[Andrew Heard]

@Andrew Heard:
hmm thanks. No useful in logs, but I think I was able to simulate this problem. Not sure why this happen, but one small change seems to fixed it, so next version as well ... (probably tomorrow).

@menion - "No useful in logs" - that's a shame because it generates huge (15MB) file and was lots of effort (long story) getting it emailed. Is there something I could do better next time? I waited until Locus crash then created the log as quickly as possible.

[menion]

@tapio:
version tomorrow .. sorry for a delay.

@Andrew Heard:
sorry to hear you had such problems with obtain of logs. It's perfect, just in this case, this method is not useful. There are two common types of problems ... crash and ANR.
Crash is when app really crash and you get dialog with "Application was terminated" (or something like this). In this case, log is useful, because in log is directly information where app crashed (not why).
ANR means "application not responding". This happen when app do too much work on background (longer then 5 seconds). Then you see dialog "Application is not responding" with option "wait" or "close". This should be your case here and log is not useful, because app did not crash, it just do something ... if you leave app for some time, it should start working again.
So thanks for a log, it did not helped for now, but I believe I've found thanks to your information a source of troubles! And now you at least know, how to create useful log (for cases when app "crash").

[Andrew Heard]

@Andrew Heard:
ANR means "application not responding". This happen when app do too much work on background (longer then 5 seconds). Then you see dialog "Application is not responding" with option "wait" or "close". This should be your case here and log is not useful, because app did not crash, it just do something ... if you leave app for some time, it should start working again.

@menion - only for my interest I tapped ANR Wait 10+ times with quite long wait in between but Locus never responded. So looking forward to next release

[TrulloF]

Hi, I get extremely slow map rendering with the newest version from Play Store. 
Any ideas, what might cause this slowness?
Xperia Z5 Compact, Stock Rom (7.1.1). Locus folder on external  SD, but rw enabled.

Btw. the issue with crashing after searching in internal POI db is gone.

Edit: Okay, it was a problem in my configuration and not Locus. Works like a charm now.

[Andrew Heard]

3.27.1 Pro: @menion:

• ANR - fixed
• icons in slope coloring - even spacing and excellent