Jump to content

AnyMules

Members
  • Posts

    115
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by AnyMules

  1. Given that a lot of users also use GSAK, it should be noted that GSAK also shows DNFs as a red dot in the "last 4 logs" view, so the consistency there could be appreciated by many. But I do agree that the two "red" shades is hard to distinguish between at a quick glance (and for those of us with bad eyesight).
  2. As a prior "other app" refugee (and I do still go back to that app for some things still - especially with its ability for me to carry around my regular 30k+ caches with logs and info in my pocket), I'm now using Cachly as my primary app. The view of how many cache logs you have done each day is one of those "other app" features that I do miss, although it's just a "nice to have" feature and not high on my wish list of improvements that I want to see in Cachly. For reference: the "other app" it's quite easy to see a tally of how many cache logs of each type (found, DNF, needs Maint/write note, etc) you have done each day.
  3. I agree with the Troll, some sort of "ready to upload" flag to mark those which are good to go, and not the others would be handy for those bulk uploads...
  4. @vanBaarsel - as @Nic Hubbard pointed out, TomTom GO doesn't currently support this feature that was available in the older TomTom app. Have a look on the TomTom Support Forums and add a comment if you think this is something that TomTom should fix: https://en.discussions.tomtom.com/tomtom-go-mobile-and-navigation-for-iphoneipad-29/url-scheme-for-tomtom-go-mobile-ios-999005 I just did.
  5. I'll add a +1 to this. The ability to put (paste) a coordinate in in a single go, rather than having to specify it in halves, would be much appreciated when editing or adding a waypoint. If it would support the addition of the coordinate in a number of different formats (DD MM.MMM, D.DDDD, DD MM SS) then that would also be appreciated as a number of puzzles and multis often use these different formats in their calculations.
  6. It would be good, especially for those people who have vision difficulties, to support "Dynamic Type" for the fonts used in the app so that the size of the font can be adjusted to be larger if required, especially on the "List" view where the text is very small.
  7. I don't have too much of a need to create my own custom URLs as most of the functionality I am looking for is already in the app (ie, Navigate with TomTom - although I would still like to see the change to have it Navigate rather than just show the location). But I have seen a number of examples on the interwebs (as also indicated by @rragan) where this can be useful for some users to call the openURL: iOS feature with an appropriate string/ command to launch a 3rd party app or Apple URL. Alternately, if Cachly added some of the more common tasks in to the app itself, the need for the custom commands would likely diminish and would only be needed by a very small minority of users with some unique URL requirements.
  8. Other apps have had this functionality previously - where all logs could be done offline, then all uploaded with a single action. They do stop at their current point if they encounter an error at any stage (ie, a find log with no text) so you can then fix that error, and then start the send again from that point onwards. I'm one that would make good use of this feature as I'm often caching in areas with no phone coverage, so using the app in an off-line mode. Once you have many logs queued up, manually going in to each one of them and uploading individually is very time consuming (I did 50+ the other day like this on two occasions on a day with over 100 finds). Especially useful when you need to go and add all the TBs in as you can't log them currently when there is no phone signal - although I know there's another feature request for that
  9. On the "Logs" page where it shows you all your previous logs, the app currently shows the GC reference number, but not the cache name (unless you press on the log). It'd be handy to see the cache name (or part of it that fits on the screen if the name is really long) next to the GC code as this would be make looking at previous logs a lot more user friendly when you can remember the cache name (i'm not someone who memorises GC reference numbers as easily as the names). At the moment, you need to remember when you logged it, then click each one around that date and time until you find the right one.
  10. A temporary workaround I'm using on this one is to include a couple of blank lines at the start of the template. This then gives a large enough area to click in above the text to put the cursor to the beginning.
  11. I've been using the updated beta version mentioned in the other post for a few weeks now. I can confirm that it does a good job of allowing people in non-Seattle time zones to log caches at the "correct" date/time.
  12. We have a good mix of both types in Australia. Some where there are letterboxes at the listed coordinate, and others where a projection or other calculation is needed in The state of South Australia they are more the first type, in the state of Victoria, they are more the 2nd.
  13. Is it possible for the Personal Cache Note to be able to be synced/updated/uploaded from Cachly? This is another of those features that I have used previously in other apps to enter notes on a cache on the phone while at GZ, but also have them available later as they get uploaded to geocaching.com. Also very handy for Multi-caches as you can then return to them another day and continue where you left off.
  14. Hey @Nic Hubbard, I spent most of the afternoon today out caching and made about 25 logs with Cachly. All logs look good date wise, so I'm pretty happy with that. I only had to refer back to "the other app" on a couple of occasions where I had corrected coordinates stored, but hadn't migrated them to Cachly (or geocaching.com) yet. So I'm pretty happy with the way this app is now working with regards to the dates. It all looks correct (although I'll probably need to test one day around the midnight cutover, but that won't be for a while yet). Thanks again for all your work on this issue!
  15. Hi @Nic Hubbard I tested it this morning and it seemed to work fine. I created a cache note for a cache at 6:00am my time which would have previously shown incorrectly and it appeared on the correct date on geocaching.com. So far so good. I'll do some more logging with Cachly at various times over the weekend and see how it goes. Thanks for all the work you've put in to this.
  16. Thanks @Nic Hubbard. I'll eagerly await this change, and use one of the workarounds in the mean time - probably "find cache using Cachly then log it with Geosphere", as that has worked for me the last few days, although it does mean that I need to keep two copies of the caches on my phone up to date - but that's not too difficult to achieve with a daily export of caches from GSAK via dropbox in to each app. Again many thanks for your rapid responses and eagerness to make your app more functional and the best caching app out there. I'm loving many of the features of Cachly.
  17. That all kind of explains why some of this is happening, but, as demonstrated, logging the cache on the Groundspeak web site (and from c:geo which we believe screenscrapes the web site) actually logged it with the correct day - so it's only looking "wrong" for anything that uses the API (apart from GSAK and Geosphere which seem to both apply a "fiddle factor" to get it right). Unfortunately, with the way that the web site works, and its interaction with other sites (project-gc.com for example), having logs on groundspeak which don't respect the timezone they're logged in means that all the stats are very wrong for the large majority of geocachers (anyone not in the same timezone as GCHQ), hence why these "fiddle factors" are being applied by apps like Geosphere, and it seems, by their own web site too. But, yes, I agree this this is more of a "Groundspeak issue" than a "Cachly issue", but isn't something that I'd think would be very easy for Groundspeak to address (given they haven't done so in the past 16 years - I'm pretty sure this isn't a new issue to them). My only hope is that an app like Cachly can be flexible enough to offer the option to correct the logs before they're sent (even if it's something that comes with a big warning message before enabling) for those of us not in the USA and wanting to use a different timezone. Without that option, I, and many others that care about stats and having things logged and shown on their actual found dates across multiple web sites and applications will still have to use other workarounds (logging caches with GSAK, or on the Web Site, or with Geosphere) and won't be able to use Cachly (or some of the other apps) to their full extent.
  18. Yep. That was my understanding too @Team DEMP. I just got him to try it for another comparison. I've also added a "write note" log generated with GSAK.
  19. Thanks again @Nic Hubbard. Your assistance and quick response on these forums (and emails) is greatly appreciated. I've had a friend who uses c:Geo on Android to put a Write Note on that cache as well, and that's showing "Today" - so it appears that either a) It is Today now, or b): c:Geo is also doing whatever is required to log the correct date too.
  20. Thanks @Nic Hubbard. Let me know when you're done with all the Test logs on GC69QD2 so I can delete them.
  21. I agree - from what I can see from all of that is that Geosphere MUST be doing some sort of correction as every other application is logging on the "wrong day".
  22. Here's the data from the GPX file I just downloaded/exported with GSAK for the logs I created on GC69QD2 from various sources. Where possible I chose a time of 10:00am, otherwise, the time was anywhere between 10:00am and 10:30am local Adelaide time. <groundspeak:log id="655550226"> <groundspeak:date>2016-12-14T08:30:00Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Test log from Geosphere to assist Cachly software developer.</groundspeak:text> </groundspeak:log> <groundspeak:log id="655550087"> <groundspeak:date>2016-12-14T20:00:00Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Test log from geocaching.com web site to assist Cachly software developer</groundspeak:text> </groundspeak:log> <groundspeak:log id="655550867"> <groundspeak:date>2016-12-14T00:05:16Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Test log from new official iPhone app to assist Cachly developer.</groundspeak:text> </groundspeak:log> <groundspeak:log id="655550691"> <groundspeak:date>2016-12-14T00:02:36Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Test log from old official iPhone app to assist Cachly developer</groundspeak:text> </groundspeak:log> <groundspeak:log id="655550622"> <groundspeak:date>2016-12-13T23:30:02Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Test log from Looking4Cache Pro to assist Cachly developer.</groundspeak:text> </groundspeak:log> <groundspeak:log id="655550405"> <groundspeak:date>2016-12-13T23:57:44Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Test log from Cachebot to assist Cachly Developer</groundspeak:text> </groundspeak:log> <groundspeak:log id="655550075"> <groundspeak:date>2016-12-13T23:30:00Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Test log from Cachly app to assist software developer.</groundspeak:text> </groundspeak:log> The geocaching.com web site only shows two of the above logs being on the correct day:
  23. Hi Nic, I'm in Australia/Adelaide (UTC+10:30), so half an hour different from Australia/Sydney (UTC+11:00). I hope that when you checked with the API that you didn't get my corrected version of the logs where I'd pasted the Cachly log text in to what was previously the Geosphere log so as not to upset the CO with a double log. I did post the data from the GPX file of the logs in my previous post before I did that. Edit: I've added some test logs to one of my own caches from multiple sources: https://coord.info/GC69QD2
  24. As emailed - from the testing I did with the beta this morning, the date issue is still there. I logged a cache (GC6AEGG) at 8:05am my time (UTC+10:30) this morning from both Cachly and Geosphere. When looking on Geocaching.com, the Cachly log (the one with the complete text in the screenshot attached) has yesterday's date, while the Geosphere log (with just an "A" in the cache log) is dated with the correct date. Downloading that data in to GSAK and exporting it to GPX shows that the dates are very different: <groundspeak:log id="655540535"> <groundspeak:date>2016-12-14T08:30:00Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False"> A</groundspeak:text> </groundspeak:log> <groundspeak:log id="655539993"> <groundspeak:date>2016-12-13T21:35:00Z</groundspeak:date> <groundspeak:type>Found it</groundspeak:type> <groundspeak:finder id="12456530">AnyMules</groundspeak:finder> <groundspeak:text encoded="False">Stopped by this one for a quick and easy find on the way to work. Thanks for the cache Team Cache Nerds. Found on 14 December 2016 at 8:05 am. Find# 3509</groundspeak:text> </groundspeak:log> PS: I've now gone back and corrected the logs/deleted the duplicate so the cache is no longer double logged and my find count is correct again.
  25. With the option to navigate to a cache with TomTom, the TomTom app launches fine and "show"s a marker for the cache location (which I'm assuming you're using a "tomtomhome:geo:action=show&lat=[LATITUDE]&long=[LONGITUDE]"), but then additional screen presses are then required to set that as the location and start navigation. Is it possible to have it changed to "navigate" to the cache (or the waypoint that is selected) using "tomtomhome:geo:action=navigateto&lat=[LATITUDE]&long=[LONGITUDE]&name=[WAYPOINT]" instead so it works similar to the Google Maps and Apple Maps options?
×
×
  • Create New...