Messages

A little later: btw. thanks for the precise testing and report. The blank panel should be solved now.

@menion - 3 recorded tracks - no further problems - well done

duplicated tracks after recording happened to me once or twice as well ... still no idea how this may happens, sorry. Does it happen always to you?

it has only happened during the "blank recording panel" issue, not since

I confirm the fix for the white bottom panel in the latest beta, thanks!

Tested on both my devices (nothing special, nothing broken on the older one). 

I don't think the Strava overlay works within Locus any more, even using your own cookie.

Steps to reproduce the visible-data-points issue:

• Phone + tablet both running 4.1.1.3 beta.  Cloud sync options on both devices are: first three items on (including "show new points"), fourth item off.
• 
  Each device contains a folder of geocaches, same name, previously sync'd, all points manually displayed via taps on folder icon.
• 
  On phone, under Geocaching Tools, Load PQs, select multiple PQs and tap Import.  (No caches appearing in more than one PQ, no overlap.)  Select that folder, and check the first and third checkboxes (delete, show).
• 
  Wait for import to finish, then for sync to finish, then for sync to finish on other device (tablet).
• 
  Result: oddity on tablet, as shown above.

Hope this helps.   Thanks, also thanks for the quick fix to the other stuff.

PS, please ignore my first "Also" paragraph.  There's too little info for a proper bug report, and it's likely just part of the main issue.

https://help.locusmap.eu/topic/improve-strict-navigation-mtb-comfort
This functionality could also be done by indicating the nearby target part with a different track style.

Now I can't duplicate the "Hide" issue either.  It seems to have gone away with the .1 beta.    (It applied to points I had manually created some days earlier in the Favorites folder.)  Now, after choosing a destination name, there's a momentary delay (new) and the details panel slides up (new) with info including the updated folder name.  Now - as expected - Hide is available and working.  Thanks!

Jestli chceš, můžeš se zkusit odpíchnout od některého z mých nastavení. Používám pro kolo různé varianty nastavené v Presetech, podle toho, na kterém kole jedu. To první je pro silniční kolo, druhé pro treking a to třetí pro toulání neznámými končinami. Všeobecně chci mít při nízké a vysoké rychlosti přehledovou mapu a při takové té courací spíš podrobnosti. Kombinuji to pak za jízdy se zámkem zoomu.

The bug I mentioned above is already fixed in 4.1.1.
Thanks!

Kann man bei dem Punkt zukünftig mit optionalen Möglichkeiten, die du beschreibst, rechnen?

Hallo Udo,
in der Version 4.1.0 sollte es integriert sein, das Update müsste heute noch im Playstore erscheinen
Gruß Wolfgang

@CabrioTourer42 My suggestion is to replace black in your icons with very dark grey. I've done this with the map icons for the new version of my Voluntary theme. That way they will work in dark mode, which generally needs low contrast icons and the difference is barely noticeable in the light mode.
An alternative approach is to replace the transparent areas with very low opacity white, such as #20FFFFFF. I've done that as well with some custom icons.


Sent from my moto g(6) plus using Tapatalk

Hello Menion,
in the latest Version the new track screen doesn't show up any more...
Best, Lucas

Button has an ugly cut shadow. Bottom bar is always on, Fullscreen mode, res. 1080x2244

There's no GPX-standard, cause Groundspeaks' .gpx files always just contains the Header-coordinates or the corrected-Coordinates in its <wpt>-Tags. Groundspeak delivers both coordinates just via API (="Update caches" in Locus)

So you can define an additional tag on your own. GSAK for example (which Locus is able to import in a correct way) notes the Original coordinates following way:

Code Select Expand

<gsak:wptExtension xmlns:gsak="http://www.gsak.net/xmlv1/6">
      <gsak:LatBeforeCorrect>48.123456</gsak:LatBeforeCorrect>
      <gsak:LonBeforeCorrect>14.123456</gsak:LonBeforeCorrect>
</gsak:wptExtension>

So Locus could for example create an additional:

Code Select Expand

<locus:OriginalCoordinates lat="48.123456" lon="14.123456" />

klar
was auch noch wichtig ist immer nur Fragen zum Betreff. Wenn andere Themen auftauchen ein neues Thema aufmachen. So findet man die Dinge besser über die Suche. Die kann man natürlich auch erst mal versuchen. Ich habe da auch viel gelernt durch die alten Beiträge.

Hast du mal mit Graphhopper versucht ?

Confirm crash problem resolved,
thank you Jiří!
Have a nice weekend,
Best, Lucas