State 'Found It' of a geocache cannot be deleted

eislady shared this question ago

Answered

Hi there,

I am not sure if this is a bug or if just don't find how to do it.

Problem is that I often use Pocket Queries together with a friend and then after importing his PQ, Locus shows me all the caches my friend has found as Found (with the Smiley-Symbol).

I remember that in an older version I could delete this 'Found state' by loading logs or updating the cache, so that I could see which caches I have found.

Is there any possibility to do this in Locus Pro 3.9.0 ?

Thanks a lot in advance!

The same question

Replies (1)

Menion ●

Good day eislady,

I you were able to simply disable found state in any of previous versions, it was probably error, not a feature.

Anyway as I test it, seems that only way is to remove "found" parameter from cache. This may be do by logging a "not found" log. So if you log cache as "not found" localy and then you remove this log in same menu, cache will be without "found" and even "not found" flag.

Anyway above method is just another "hack". Generally Locus do not allow to simply remove "found" information.

Hope I helped as least little bit.

URL

eislady ●

Hello Menion,

this works for me. Thanks a lot!

But it is a bit annoying to do it for every single cache. Before I could just mark every cache (normally about 500-1000 caches) in a folder and then click Load logs (I use the German version, where this button is called 'Loggs herunterladen', I don't know the English name) and all the found parameters were updated from my GC profile.

I would be very glad if this will work again in future.

URL

Menion ●

Understand, but this system is not a clever as it may work simple incorrectly.

Imagine you log a cache in Locus offline and your log is not yet on geocaching server. Then you update logs and cache "Found" state will be lost? Weird...

To be true, your use-case is quite special and I'm not sure, how many users use it's geocaching accounts in this way. So for now I have no better solution, unfortunately.

URL