Jump to content

Nic Hubbard

Administrators
  • Posts

    3847
  • Joined

  • Last visited

  • Days Won

    388

Posts posted by Nic Hubbard

  1. Cachly uses an iOS/Apple API to get the pin location from coordinates. I have a feeling something has changed on their end.

    In 2.1 we will be doing our own coordinate parsing so there will be no issues affecting the placement.

  2. 7 minutes ago, Scarch said:

    I'm running into similar problems. I've copied coordinates from an email, manually typed coordinates, and also dropped a pin in cachly and selected copy coordinates dates; after which I pasted into cachly search. Cachly responds by dropping a pin about 20 miles away.

    What device are you using? Does this happen every time you search for coordinates?

  3. 3 hours ago, Buckshot/MamaLlama said:

    This is how it has been since I first downloaded the app and started using it around mid February of this year.

    So strange. Very sorry that this issue is happening, we really have never seen it before. 

    Do you happen to have a second device to test this on with your same account?

  4. 7 minutes ago, Buckshot/MamaLlama said:

    Yes.  Every time I change any of the settings, they will all revert to the default setting after the app has been closed and then reopened.  I have even had this happen when the app has been open for awhile.  If I remember correctly, I noticed it right after one of the times that the compass wanted to recalibrate.  But, it always resets after closing and opening again.

    Have you changed usernames on geocaching.com? This is the only thing I can think of that could possibly be causing the problem, since saved Settings are per-username.

    Can you logout and log back in and see if the issue persists?

  5. 23 minutes ago, rragan said:

    I looked for a Refresh or Update action. Pull down was not intuitive enough though I am aware of it. Maybe add a backup menu item. Why shouldn't a successful drop remove it anyway? That seems like an obvious one to just handle. 

    Totally agree. Will add a refresh button as well as remove the trackable from the list when it is dropped. :)

  6. 8 minutes ago, rragan said:

    I am ecstatic. I wanted this but never figured it was likely to happen so I never asked.  Is it SQLlite?

    Cachly has always used SQLite from the beginning. But it wasn't built for performance, speed, etc.  And no unified DB.

    This all changes in 2.1. 

  7. 16 minutes ago, hidegoseek said:

    However, when I update that offline list in Cachly my notes are overwritten in the process.  Will v 2.1 merge the description instead of overwriting it?  

    Yes, it will do a merge.

    Do you know why iCaching doesn't place that into a Personal Cache Note instead? Adding it to the description doesn't seem like the best idea...or is this a Cachly issue?

  8. 2 minutes ago, Team DEMP said:

    Or is the unified "offline" database just used when offline and anything "live" isn't referencing the unified database?

    Live will always be pulling new data from the API/website. You can always save live caches to offline and it will merge the cache data if that cache already exists in the database.

  9. In Cachly 2.1 we will be using a unified database for all offline caches. This means that if you have the same cache in two different offline lists it really is the same cache in the database. Updating it will update that cache in all offline lists as well. 

    A few things to note:

    • Deleting a cache from one offline list will not remove it from others if that relationship exists. It will only be completely deleted when there are no more relationships to an offline list.
    • An upgrade process will be used to upgrade the old database to the new way of doing things.
    • Performance is massively improved over previous versions of Cachly. Lists over 50k caches can be viewed in seconds.
    • Importing GPX files will first check the database to see if those caches already exist and will not create a second copy if they do. Additional data from the GPX caches will also be merged if needed.

    Any questions or comments are welcome!

  10. Just now, cuddlefish said:

    Thanks for the reply. That's disappointing because that's not quite what I had in mind. Oh well.

    I do not think that iOS is able to integrate in any other way that I have seen. There would need to be a specific software development kit from Garmin that Cachly could tap into. :(

  11. 6 hours ago, finkenmann said:

    @Nic Yepp. It helped a little bit. But still hard to see a difference. Specialy in sun light. Other apps are looking horrible because it changes the colors a lot.

    We will continue to evaluate how we can improve this for users.

  12. 2 hours ago, rragan said:

    (This seems to use Google features to accomplish. Not sure if IOS can get at it but routing is nice albeit hard)

    Just a specific note about this. When Cachly first came out we had in-app routing, but quickly realized that giving users the option to use other routing providers was much better. Leaving that function to apps that do it best, and can provide more than we can.

    2 hours ago, rragan said:

    Option to control or disable clustering when there are lots of caches on map

    This has been added to 2.1 already and is in testing. There are also fine grained controls for the clustering params.

  13. 7 minutes ago, Mt's said:

    Is there an option to change the map to orient itself to have the cache at the top of the screen when searching for a cache??

    Tap the current location button (bottom right of map) to cycle through the various follow modes. One of the modes rotates the map based on your heading, but none of the modes force the map to have the cache at the top of your phone.

×
×
  • Create New...