Jump to content

Nic Hubbard

Administrators
  • Posts

    3973
  • Joined

  • Last visited

  • Days Won

    409

Posts posted by Nic Hubbard

  1. 16 minutes ago, Team DEMP said:

    For me, I'd say a 25x25 square mile area is probably the absolute biggest I'd look at on a cachly screen. Maybe others have a *need* to see all of a country like in the video but I definitely don't. I don't see myself needing to see an entire US state at one time. But if there is a need or a viable solution could allow for it, then great. If not, maybe a smaller coverage area should be the target to come up with the best solution

    I think regardless of the viewing size, if it is a full country, state or even just a city that the solution I posted proves to be interesting, but not practical. It was fun to build, but as much as I would like to be able to implement a simple solution like this, I can see how it won't work.

  2. 3 hours ago, c-ray242 said:

    Altough I would prefer the app to store the waypoints on the phone when used offline.

    This is the current behavior. Although as others mentioned if it detects a small amount of signal it will try to upload.

    When there is no connection it will save the Waypoint offline and then upload that waypoint at a later time (if you return to Cachly later with an internet connection they will be uploaded). 

  3. 5 minutes ago, thebruce0 said:

    Yeah red seems 'bad'. Archived is more neutral. I'd Archived should be black, and notes grey. Consistency would imply NM would be red or orange for potential problem, and Owner Maintenance perhaps green, good-to-go.

    The original colors in Cachly (besides found and DNF) were based off of the geocaching.com icons. The archive icon is red, so that is where the color was sampled from.

  4. 4 minutes ago, rragan said:

    Can you make it more fault tolerant so it can deal with a missing comma. Also will it accept d.mmmmm ( decimal degrees) and degrees/ minutes/seconds? This hearkens back to a general coordinate parser. 

    It currently uses an iOS coordinate parser that, as you have seen, its't very friendly. Implementing the new parser hopefully will be in 2.1.

  5. Clustering. This is a touchy subject. I too hate the idea of clustering pins on the map, and I know many do not love that the official app forces clustering of caches.

    The reason for this topic. In Cachly 2.1 there have been some major performance improvements. Some users use Cachly in different ways, and some might have 20,000 caches in an Offline List. I have tested 50,000 caches with no performance overhead when loading the Offline List in list view.

    However, how does one display 20-50k caches on a map? Currently trying to do this uses so much memory even an iPhone 7 crashes. Putting that many pins on a map just isn't feasible. This is where the idea of clustering come into play.

    Here is what I want feedback about for 2.1:

    • Offline Lists will use clustering by default if the list has more than 1000 caches.
    • Clustering can be turned off for ALL lists with a warning that it might not be possible to show all the caches you want on the map, and it might be very slow.
    • Offline Lists will load in List View by default and not even load pins on the map if the user doesn't want to look at it, thus improving performance.
    • Other alternatives to clustering? So far, I have not gotten far with this.
  6. 3 hours ago, dukeofurl said:

    4) Automatic emails from Groundspeak, links in there, is there a way to make them open cachly instead of the groundspeak app?

    Yes, this isn't possible because Groundspeak owns the coord.info domain, which is tied to their app, and only their app.

    3 hours ago, dukeofurl said:

    5) When searching for a cache via the GC number, is there a way to make it automatically think that I'm typing GC in front of the code, even though I'm not?

    Since that field takes GC Code, coordinates or a location search there isn't a way to do this.

×
×
  • Create New...