This object is in archive! 

Download of geocaches with geocaching4Locus: Confusing behavior

rvheddeg shared this problem 11 years ago
Solved

Display all your geocaches in a category.


Download some geocaches with geocaching4locus:


When its finished you have the choice "Display on map after the import"


- if you check this, the downloaded geocaches are displayed on the screen, but all the others are not. When you go to the data tab you`ll see that all the geocaches are still checked and that there`s no filter selected. It`s only when you first deselect and then select them all that they are displayed on the screen again. (restarting Locus has the same effect) Is this by design? It`s rather confusing.


- If it`s not checked, then all the downloaded geocaches are NOT displayed on the screen, even if they were before. If you go to the data Tab, there you`ll notice that the checkboxes are indeed not checked. That`s consistent, but it confuse me one`s again what the use case is. Why download if you don`t want to see them?


Android 4.0.4 and 2.0.5


SGS2

Replies (5)

photo
0

Same here...


I noticed this behaviour with one of the last (Locus) updates.


BTW, you don`t have to deselect the caches in the data screen, just selecting all (even if they are selected) let`s them reappear.


(Android 4.2.1)

photo
0

Hi guys,


thanks for report. You`re absolutely right that this is quite confusing and mainly, it`s not intent! Rather issue that I do not notice ... fixed now!

photo
0

Has this behavior returned?


When I receive an email from geocaching.com with new geocaches, I click on them and choose "Import cache in ..."


This hides all other geocaches, but they are still checked when I look at them in the data.


It`s only when I uncheck and recheck them all that I see them again...


Any idea?

photo
0

Yes, I could reproduce this with the latest (released) version 2.13.1.


I`m sure Menion will have a look at this... ;-)

photo
0

thanks guys. I did quite a lot of changes to make points loading/unloading much faster (hope you noticed this ;) ) and this is remaining issue from this task. It will be fixed in next version

Replies have been locked on this page!