Ah! No, not that old chestnut!...caughtatwork wrote:Pretty much comes up each year and ... no.quiet1_au wrote:New feature request - Moveables Inventory
I'm not expecting this for this year's race, but what I'm finding is that as I query for Bingo caches unfound by me, it's not quite so easy to determine which caches you (should) still have in your possession and in doing so get a quick way of accessing the logging page for a particular cache you have. (Along the lines of the Trackables option on t'other site) Would something like this be possible?
Well, not fully no, but not completely yes.
In order to move a moveable into your inventory you would need a secondary action which was (say) "Taken". A mere find does not tell anyone whether it was taken or left behind. The "Taken" could be done via log or via tickbox on the log page for the found or noted log.
You would then need to take another secondary action on a move to "Leave" the cache, removing it from your inventory.
The challenge we have encountered in the past is that "Taken" and "Left" log types are not handled by any GPX file reader. We're also entirely unsure of what errors will occur should we put out these two new logs. e.g. GSAK when reading the file may fail spectacularly. Your GPS may not read the file and lock up your device.
What will also happen is that someone will forget to log (or action) a "Taken", leading people to believe it's still there whereas it's not. Ditto for the "Leave". You forget to "Leave" the cache and it appears to be not there.
There is no simple solution to any of this sort of problem. It's one of those things where you need to do the work to see if you want to go looking for a cache.
What I was meaning is list of moveable caches that I've logged a "found" for but not yet posted a "moved" log for, in one quick & easy-to-access list (like the trackables inventory). Working though the daily logs to find a cache to log a move for is a bit of a hassle as they appear to be sorted by GCA code rather than date/log order? It's particularly bad on a tablet device which has limited screen space and doesn't really handle tabs that well. It's more of a problem in the first few days of the race when there are lots of caches to log, but not so critical when you're down to a handful a day.
Just wondering.