Messages

switch gps off an you´ll get what you want

Thx, good workaround. 😉

... but in the version before there was no need to do this,

When I use 'nearest caches' in newest version of geocachin4locus the coordinates are not set to the cursor position.
In the old version I could point in the map to the location I want geocaches to download ... and coordinates where sent from Locus to geo4loc to that point.
This was an easy and quick way to fill a far map area without a pocket query.
Is this a problem of Locus or geo4loc (or maybe a user problem 😚)

In your geocaching profile -》settings-》authorisized/trusted  apps ( don't see the english word) ...
You can see if access is granted to geocaching4locus ... maybe you can see there something helping infos.

Hmmm, for me it's working on two different devices in Pro and Beta.

... and it's faster then Locus with loading map parts. 😉😁

... and the new version is online .... and seems to work.   

Just upgraded to 38.2 ... and the crash is gone. 

BUT it is not possible to use a V4 map.
The screen creates only partialy tiles ... and with zooming some of them disappears while others occurs ... 

Just updated to version 3.38 from 27.5 ...
The first start has worked.
Then I switched from an old LocusMap to new V4 Vectormap ... and I had my first crash.

Now every start of LM pro leads directly to a crash ... 

Now on every start it reminds me again

Same to me ...

It seems as if geocaching life map doesn't work in routeplaner anymore.
Normally I activate it in the map then switch to routeplaner and can see all the geocaches  along the road when creating a new route.

Zooming with hardware buttons doesn't work in route planer ...

There seems to be a numbering problem in route planer:
When creating a route with planning points ... then create a via point ... the via point gets a lower number then last planning point.
Pic1: 4 planning points
Pic2: new via point

PS: checked it in 3.37.2 ... there is the same poblem.

30 seconds is from my point of view optimal limit to prevent too frequent recalculation. And years of usage confirmed this .

No problem  ... 

PS: can I change the value (30 sec) for delay time of recalculation  in config file?

Would be good for testing ... and maybe even in field ... because:
If Locus doesn't lead back I'm normaly back on route after recalculation. In other case my setting 'distance for recalculate' would prevent from immediately calculation.

Did some (couch-  )testing too ... and in many cases it works pretty good.

Only one time it leads me directly back to my starting point  ... but I couldn't repeat this ...

I think it's time for field test ... (when rain stops  )

Right.