New Topic

Locus Map - help desk Topic Problem Other add-ons

Category Other add-ons

Tags multi cache solver, refresh, waypoints

Comments 7

Subscribers 5

Votes 3

Multi cache solver doesen't refresh waypoints, if you change variables

Nicolai shared this problem ago

In Progress

Hello

If you change variables in the multi cache solver, the waypoints of all stages will not be refreshed. Would be nice if this problem will be fixed.

Thanks in advance!

The same problem 0

Replies (5)

c.s.g. ●

Hi Nicolai,

maybe you can get a faster response to your problem if you post it here:

https://plus.google.com/communities/113063786196810493588

Though many posts are in german, english is no problem in that forum.

c.s.g.

Reply URL

Nicolai ●

Okay thanks for the information

Reply URL

rvheddeg ●

I think this issue is also a bug in Locus. How is it possible that I see multiple waypoints for a cache while I couldn't see them in the waypoint list?

See multi cache solver forum

Version 3.21.1

Reply URL

Menion ●

Hi guys, rvheddeg,

are there any exact steps I may follow to simulate this problem in Locus Map? Thanks

Reply URL

rvheddeg ●

Hi Menion,

To reproduce:

Select a geocache and press Calculate to open the solver
Make a new waypoint in the addon.
Set the coordinates to whatever (but keep it in the neighborhood to see the effect)
Quit the addon and go back to Locus map (you can see the waypoint now)
Go back to the addon
Change the coordinates of the waypoint
Quit the addon and go back to Locus => you can see 2 waypoints on the map now!

=> Please move the original waypoint or remove it. The cache has now 2 waypoints, but displays only one in the waypoint list.

Version 0.72 of the solver

Version 3.22.1 of Locus

PS: If you follow the link you will see the same steps, but I have copied them here.

Reply URL

Nicolai ●

Yap, this is exactly the same prolem, I have too

URL

Menion ●

Hi guys,

thanks for a precise description. Issue on Locus Map side will be solved in next version. Not sure if this is solution also for initial problem wrote here ... you will see in next (Beta)version.

URL