yes something along these lines can be done. using custom implementation for caching anyways.

that is something where I always debate with myself what I want...

let's see what votes it gets but a simple quick fix is to tap on the cache icon (bottom right on map) and select center on cache.

it allows you to get there with 2 extra clicks but does not do anything automatically.

compromise?

not a fan of requiring close proximity. but one could implement something similar to sharing of wpt data. will think about that too

I like that idea :-) and yes what you propose is almost workable.

new beta allows copying of coordinates from any waypoint. and editing wpt allows freeform entry where that exact copied text can be pasted.

allowing what you request would be a bigger impact on the flow within GCDroid so it might not happen. I might allow storing any wpt online though (not as corrected).

I think with the copy paste it could be a compromise?

just don't really see use for it. neongeo is dead and cgeo has no access to api so they need to do their own thing.

given the fact that I can store corrected coords for ANY cachetype I don't see why I would try and parse the note.

it also makes it impossible to show the map fast and correctly since I clearly don't want to check for a stored note before hand.

so this get's a likely no from me

yeah I like that idea :-) And I think I already have a timestamp.

Let's say 90 days sounds reasonable? Or 60?

Guess anything beyond that means you're not using the data and it can be purged.

Ich koennte vibrieren (naja das Telefon :-)).

Mal schaun was sich da machen laesst.

I think this meets the needs of 99% of my users.

How many caches around you really have more than 200 favorites? Maybe you happen to be in an area where you have 10?

Entering a number leaves room for too many issues (enter letters, nothing, etc).

I don't see the need to go beyond 200 realistically.

Given the fact that I spend 1000s of hours on this app and probably got about $0.00001 per hour so far I believe spreading the word isn't much to ask.

I will consider removing it and simply increase the price or just stop developing it all together.

I will think about what to do here for the next major release that will contain the new API.