Jump to content

Nic Hubbard

Administrators
  • Posts

    3970
  • Joined

  • Last visited

  • Days Won

    409

Everything posted by Nic Hubbard

  1. This shouldn't be happening. Are you able to delete Cachly and reinstall? This isn't an ideal solution but it could help in this situation. What is your GC username?
  2. Yes, private browsing is what I would check. That keeps cookies for just each tab.
  3. Sadly Groundspeak doesn't allow third-party developers to add this to their apps. They said it was a privacy issue.
  4. Great suggestion. I have this on our feature list and will see how hard it would be to develop.
  5. Yep. I realize the need for this feature and that many many users are wanting it. Just don't want to release it prematurely.
  6. I do agree this would be a great feature. However, it would take a large amount of development time and testing as syncing is a hard thing to get right. It is for sure on our feature list.
  7. This is something that we have on our feature list to add, but not sure when it will make it in.
  8. Got it. I think this would be a nice feature addition.
  9. When Cachly loads caches as search results, it loads "Lite" caches. In order to show the 5 dots we would we would have to load "Full" caches which would use part of your 6000 full caches per 24 hour limit that is imposed by geocaching.com. (Users can load 10,000 Lite caches per 24/hours) We have considered using a Settings option to allow users to do this, but it hasn't been planned yet.
  10. Glad it is working so well for you. We will be submitting 2.0.2 to Apple today.
  11. I totally agree. However the API does not provide this info, so there isn't currently a way to do this.
  12. It shouldn't be too hard to automatically make the cursor start at the beginning of the text, so I will fix this.
  13. This is a feature that has been on our list for a while now. Just have not had a chance to add it. Hopefully in 2.1. Can you explain the issue you were having with the default log text in Cachly?
  14. This is an issue that was fixed in 2.0.2 which we will be submitting to Apple this week. Stay tuned.
  15. This is something that we are working on fixing. Basically we need to be updating the entire list for each GPS update we get. However, if it is a massive list this might have some performance ramifications, so we are working through this.
  16. I think the API has always worked this way. There is an option when we request caches to return caches that are archived or not. So I think it is intentional.
  17. Some event caches will still show up even though they are Archived. This is the real reason for this feature, was to hide those.
  18. This is actually something we introduced way back in 1.0.4, but the overhead of converting logs with markup to attributed text was causing some performance issues. After that, we determined that few logs even use Markup, so we removed the feature and kept it on our feature list to fix the performance issues and add it again in a future version.
  19. Yes, this is a feature that we have been working on. However it isn't a quick and simple thing to add. Here is what has to happen with this feature: Upload pending logs, one at a time to the server. If pending log has a trackable to log, log each trackable one at a time. If pending log has images to upload, upload images one at a time. So there are quite a few working pieces to this feature. That being said, we are still actively working on it.
  20. This is something that I have wanted to add for a while, so I made sure that I added it in for 2.0.2.
  21. Thanks for reporting this extra detail. Will test this today.
  22. This is a great feature request, and something I have wanted to add for a while.
  23. Yes, as stated the 2.0.2 update will include this fix. We have to wait until to the New Year to submit the update to Apple since they are closed for the holiday.
×
×
  • Create New...