No, it can perform up to 20 requests per 60 seconds, each with 50 caches in the request. Cachly just has to wait for all of those to complete, and if you more requests are needed it does have to wait 60 seconds.
The problem is users complain either way. In 3.0 you did have to tap Save in order to save the Note but users complained about that and wanted to go back to the old way, where it was uploaded automatically.
Really don't think we can make everyone happy with this one.
Yes. Previous versions used your username as the "key" to fetch both of these from the database. This was sometimes problematic in certain situations. So 3.1 removed this requirement and doesn't use a key. Because of this it is possible to see old offline lists or logs that had disappeared into the database black hole.
My math for calculating miles to meters (we use meters to do the coordinate conversion) was a bit off. This will be fixed in 3.1.1.
Sorry about that, but thanks for catching it!
There just isn't a way to do this using the API that we are provided. In 3.1 you will be able to filter your logs by log type, this will hopefully help a bit.
Pull down on the logs screen to load more from the sever.
Setting the State to Ohio, and using those dates it shows me two caches. Have you cleared your search options to make sure nothing else is coming into play?
Sorry, realized it is in 3.1. Been using that version too long.
No there is not.
Correct. Cachly is a portrait only app.
Hints are just plain text, so they don't need the additional options.
This is just the nature of having the note in the database as well as online. Cachly should be syncing to the server, you just will have to remember to refresh the caches if you do make note changes on geocaching.com yourself.
This would be an incredible amount of development. Not something that I would want to do.
Are you saving these without an internet connection? If so, they will upload later, if not, they should upload right away. Is this not happening?