This object is in archive!
Modified geocache setting are not refreched
Not a Problem
Hello menion
if i modify
settings/Geocaching/Automatic waypoint loading/
and select one or more wpt types
on next start of locus they are displayed on map.
Next i revert my selection.
On next start of locus the waypoints are furthermore displayed on map > show last state?!
solution for now, long click on "Data icon" > hide temp map items
The same problem 
Hello balloni,
the current behaviour is the intent. It is as you wrote ... upon next start, app restores state of all visible caches/waypoints. Settings we talk here about is applied only when you try to load a new cache, that does not have any visible waypoints. This is from my point of view most logical system ... the old existing state is preserved, on new points is applied this setting.
Does it make sense or you expected different behaviour? All visible caches reload based on this settings?
Hello balloni,
the current behaviour is the intent. It is as you wrote ... upon next start, app restores state of all visible caches/waypoints. Settings we talk here about is applied only when you try to load a new cache, that does not have any visible waypoints. This is from my point of view most logical system ... the old existing state is preserved, on new points is applied this setting.
Does it make sense or you expected different behaviour? All visible caches reload based on this settings?
Hello menion
>Does it make sense<
"last state" generaly yes, but not in case of changed settings
>or you expected different behaviour?<
in case of changed settings > yes,
i expect to see the result of changed setting after restart of locus
how should a basic locus user understand and solve this behavior??
long click on "data button" is a well hidden feature and as i know not described or also well hidden inside manual ?!
Hello menion
>Does it make sense<
"last state" generaly yes, but not in case of changed settings
>or you expected different behaviour?<
in case of changed settings > yes,
i expect to see the result of changed setting after restart of locus
how should a basic locus user understand and solve this behavior??
long click on "data button" is a well hidden feature and as i know not described or also well hidden inside manual ?!
Hello,
how should a basic locus user understand and solve this behaviour??
Question for me is if basic user needs to solve this problem. I do not know, never discuss this with anyone, you are first :).
So your solution: after a change of settings, hide completely all waypoints of all caches and reload waypoints of all visible caches with new settings? It is probably doable, but I do not know, do I really wants to forget the state of all waypoints and apply on the new settings? I almost never change this setting, so for me, it is really hard to decide.
Hello,
how should a basic locus user understand and solve this behaviour??
Question for me is if basic user needs to solve this problem. I do not know, never discuss this with anyone, you are first :).
So your solution: after a change of settings, hide completely all waypoints of all caches and reload waypoints of all visible caches with new settings? It is probably doable, but I do not know, do I really wants to forget the state of all waypoints and apply on the new settings? I almost never change this setting, so for me, it is really hard to decide.
Hello guys
Personally, I never used this filter for WP. It does not really matter to me.
I use touch and hold to remove and download WP again.
I'm always downloading all WPs. Often it happens that they are incorrectly assigned or exchanged by WP. That's why it's safer to see them all.
Current behavior of Locus seems logical to me. Also for an ordinary user.
#s3gt_translate_tooltip_mini { display: none !important;
Hello guys
Personally, I never used this filter for WP. It does not really matter to me.
I use touch and hold to remove and download WP again.
I'm always downloading all WPs. Often it happens that they are incorrectly assigned or exchanged by WP. That's why it's safer to see them all.
Current behavior of Locus seems logical to me. Also for an ordinary user.
#s3gt_translate_tooltip_mini { display: none !important;
Thanks Condor for your opinion.
Maybe it is not perfectly obvious (cannot now remember that some new user complains on this behaviour), anyway I still think that keeping visibility of already visible waypoints as was, is more logical then reload all waypoints based on new settings. So for now, it stays as is.
Thanks Condor for your opinion.
Maybe it is not perfectly obvious (cannot now remember that some new user complains on this behaviour), anyway I still think that keeping visibility of already visible waypoints as was, is more logical then reload all waypoints based on new settings. So for now, it stays as is.
Replies have been locked on this page!