Jump to content

barefootguru

Members
  • Posts

    265
  • Joined

  • Last visited

  • Days Won

    24

Posts posted by barefootguru

  1. Does anyone use the newish drafts feature for this?  Maybe it’s a topic for the wiki B)

    Seems like I could use drafts instead of pending logs, then be able to edit & submit from any device/browser?

    But knowing GS there’s probably caveats!

  2. I meant adding some text explaining you need to request access to edit the wiki.

    It's off-putting having your edits silently ignored, and people are used to wikis allowing changes.

  3. Cachly does make its entire database available through iTunes (device > File Sharing > Cachly > Cachly.sqlite), and I suspect the DNFs will be in a separate table, but you'd have to know SQL to go that route.

    Personally, even the living aren't that interested in my hobby :lol:

    p.s. looks like you can get a list of DNFs which haven't subsequently been found with GSAK https://project-gc.com/qa/?qa=8983/search-dnfs-not-subsequently-found, which could then be exported.

  4. On 26/02/2018 at 1:21 PM, wuthred said:

    The My Finds PQ only includes DNFs for caches eventually found. Cachly has all my DNF logs. Is there any way the Logs feature in Cachly could export everything in CSV format for extracting in a spreadsheet? Or please tell me it already exists. Thanks. 

    You can see your DNF logs through the website, though it also includes those you’ve subsequently found.

    https://www.geocaching.com/my/logs.aspx?s=1&lt=3

  5. I think there's a date bug in the Date Downloaded filter, maybe because I'm in New Zealand… and currently on daylight saving — NZDT, UTC+13.

    I'm looking at a cache which says 'Downloaded on 20/02/2018 at 11:59' (which is correct).

    If I create a filter with Type=Date Downloaded, Date=19/02/2018, Logic=Earlier than or on, Invert Filter=No; then I still see the cache.

    If I change the date to 18/02/2018 then it's hidden as expected — so 2 days out?

    Cachly 4.0.1, iOS 11.2.5

  6. 3 hours ago, Nic Hubbard said:

    No, this isn't true. That message is shown if you have exceeded 30 API requests in the last 60 seconds. There are instances where you would have already used some API requests, e.g. loading caches in Live, viewing an individual cache etc. that could have caused it to appear.

    Since Cachly 4, I'm no longer receiving the waiting message when updating (pretty much) the same set of caches — so it's definitely slower :rolleyes:

  7. Should it start with Cachly?  The only ones I can see are Cachly.cpu_resource… I've just e-mailed the latest of those.  The timestamp looks around the start of the update rather than when Cachly crashed though.

    BTW it's actually significantly slower now:  I wasn't timing but it's gone from 5-10 mins to 30-40 (before it crashes).

  8. Since upgrading to Cachly 4, it crashes when updating one of my offline lists:  around 2000 caches, doing a full update of all caches.  Cachly takes about the right amount of time, then crashes.

    Could only find Cachly.cpu_resource logs in Analytics, not a crash… hmm, unless iOS quit Cachly because of the CPU usage?

    iPhone SE, iOS 11.2.5

  9. FWIW I'm experiencing the same slower time downloading PQs.  I update my iPad — still on previous version, and iPhone — on latest version, at the same time, so it's not a network issue.  The 2 devices used to take about the same time, the iPhone is now significantly slower (twice as long?)

  10. I spend 15 minutes a week keeping my 'Unfound' offline list updated from pocket queries:  I have around 3,000 caches which covers an area ready for any spontaneous day trip — I can use it to both move around the map and caches are stored locally in case cellular service is unavailable.

  11. Yeah, Google (actually DuckDuckGo) confirms that NSPredicate has to match the entire string.  I do think this will trip people up, as no ^ $ is present.

    I like @rragan‘s idea of stripping ^ $ if present and enclosing the string in .* but maybe that’s too complicated, and an explanation on the screen saying the expression is automatically enclosed in ^ $ would suffice.

×
×
  • Create New...