-
Posts
3837 -
Joined
-
Last visited
-
Days Won
388
Posts posted by Nic Hubbard
-
-
7 minutes ago, ciarmer said:
I'm just mentioning it because other refugees who don't find the GSAK path or don't use GSAK, may have a problem with it if you decide to remove the find count keyword.
Don't worry. I won't remove it.
7 minutes ago, ciarmer said:I hope you don't mind, but as a refugee, I will probably be asking about things that I've grown accustomed to using Geosphere when I don't find a similar capability within Cachly. I hope you don't take those questions as critical commentary; rather as positive queries meant to potentially improve Cachly. From everything I've seen so far, Cachly is wonderful. The developer of Geosphere seemed to place great emphasis on offline data and GSAK integration - so that's where most of my future questions will probably center. Again, none of it will be or should be interpreted as critical criticism. I hope you understand.
Not a problem. Keep it coming!
-
This keyword is proving to be very frustrating. I am almost tempted to remove it since it is such a tricky one to make work correctly.
Thanks for the comments, I will add them to the bug report and work to fix it.
-
-
Thanks, I will look into it as well.
-
32 minutes ago, jinta29 said:
Ok, fantastic. How do you do this? I can't for the life of me work out how to merge the pq's. Thanks
You need to be using 2.0. If you are, just swipe the row on one of the PQ's that is in the Offline tab. Then choose "Options". This will give you options to copy, merge etc with another list.
-
Welcome to Cachly!
2 minutes ago, DSimm626 said:Friends list: This is a c:geo thing I believe. When you view a cache, you can also see if any of your friends have found the cache. The friends list comes from "Your Friends" list on geocaching.com. A older version of GeoSphere would show your log(if you loaded a cache you found) and the logs of your friends.
This has been requested by other users, but in looking at the various API methods that we have available to them it doesn't seem like an easy thing to do. We are still investigating this.
3 minutes ago, DSimm626 said:Field note templates: GeoSphere lets you create FN templates so when you log a field note you don't have to type the same thing over. This is great for when you are caching with someone you can already have this part in your log. Also great for copy & paste logs on power trails. GeoSphere also lets you add local date/time and find count to your log. I always 'sign' my geonick and where I am from on all my logs.
Cachly has this. Just go to Settings and you will see the log defaults option. You can also insert keywords for various things.
-
-
Is this only happening for field notes? Or also for published logs from Cachly?
-
I have been talking with Clyde from GSAK about this issue and seeing how they fixed it. He has some great insight has he has been dealing with this since 2011 or maybe earlier. He provided some links with much more background on this issue:
-
Are you force quitting Cachly, or is iOS doing it when it needs memory?
Saving application state is something that is on our list. Working on feature priorities right now for 2.1 so will see where that comes in.
-
Having it open in Safari is a quick fix and I think that there are good arguments for this, so I will get it fixed right now. Won't be in 2.0.1 as we have already submitted that, but will be in 2.0.2.
-
7 hours ago, jinta29 said:
Is there any way to view multiple PQ's on the offline maps? My current PQ's for the state number 13 and I would like to view more than 1 PQ at a time. Thanks
There isn't currently a way to view more than one PQ at a time, but you can merge lists so that you can create a "master" PQ list.
Just make sure you are using version 2.0.
-
1 hour ago, ciarmer said:
Are there plans to include a way to upload in bulk? It doesn't take too long to upload five caches individually, but it might get a bit tedious if one has 20 or 30 finds waiting to be uploaded as field notes.
Yes, this is a feature that we have been planning for a long time, but it just didn't make it into 2.0. It is now planned for 2.1 which is now being worked on. Stay tuned!
-
As you mentioned, it is a hard thing to keep track of. Are you using version 2.0?
In 2.0 there was a number of fixes to make this keyword more reliable, but as you have stated there are still issues. I will look into it right away and get it fixed.
-
2 minutes ago, AnyMules said:
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.
Happy to help!
-
46 minutes ago, AnyMules said:
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.
Yes, I think adding an option with a big warning about this is what we will do. Still working on the specifics, so it might not be for a little while until we release that version.
Thanks for everyone's input.
-
This option will actually need to come after 2.0.1. Working now to schedule it.
-
-
Yes, this feature is being added in 2.0.1. It is currently just a "quick search" and not the full filtering functionality that we will be adding in 2.1.
-
45 minutes ago, Team DEMP said:
What you noted and were told was my assumption too. There was a thread I'm sure I can find where someone claimed they were told by a GC developer that it required updating/data migration, etc which didn't make sense.
This possibly could be the case for very old logs. It might be that very old logs are not UTC.
45 minutes ago, Team DEMP said:So if they properly store it as UTC, then they need to add in a view of the data using either browser/device timezone or a new account setting for timezone which just effects the display. The underlying data remains UTC.
There is a Time Zone settings already on geocaching.com, but I really don't know what it affects. Would be curious to know.
-
9 minutes ago, Team DEMP said:
You findings match the analysis in the threads I've reviewed in the Geocaching forums. I also had a pretty rough discussion in one of the threads where others, not in the know, claim it must be a HUGE issue because GC hasn't done anything to fix it. They claim it requires updating all data, etc. I completely disagree based on way too many years of implementing technology solutions and I expect there are multiple ways to address the situation.
I do not think that it would require updating all data. From what I have seen personally in the API and been told by the Groundspeak developers, the log dates are clearly stored as UTC dates. The real "bug" on geocaching.com is that it isn't taking the users set time zone into account and doing a conversion from the UTC date into the users localized date/time.
Jason, one of the Groundspeak developers told me he put it on their list and they will be looking into the issue.
-
After doing more testing, and thinking about this more, I have come to the conclusion on a few things:
- Geosphere is doing UTC timezone manipulation to appease geocaching.com.
- Cachly is sending the correct UTC time for the log date. UTC time is the same in every timezone on earth since it is a calculation of seconds since 1970.
- geocaching.com should be taking the UTC time and converting that to the localized time zone set by the user in their geocaching.com settings. This is currently not happening.
- If and when geocaching.com fixes their UTC date issue, all manipulated Geosphere logs will be incorrect.
- If Cachly manipulated UTC dates based on the timezone, when geocaching.com fixes their UTC issue, these dates would also be incorrect.
With those points in mind, I will be keeping our logging date the same. I don't want to manipulate the date so that geocaching.com "looks" correct, but the UTC date in the database is incorrect.
Thoughts?
-
1 hour ago, brudderman said:
I believe you have previously given a target date for the 2.1 version but haven't been able to find that post. Is it after the first of the year?
There hasn't been a date set. We are just finishing up 2.0.1 and will be starting work on 2.1 very soon.
-
Thanks guys. Will report back in a few hours when I get a chance to test everything again and some new time zone offset code.
Viewing pocket queries
in General Questions
Posted
Simplicity and intuitiveness sometimes go hand and hand, and are sometimes at odds. We have tried to keep both in mind on this screen. There are a lot of controls that a user can invoke, but I think that the screen still works.
We are using the standard iOS swipe to reveal feature, which is used throughout iOS. The iOS Mail app does this exact thing, and this is what Cachly's Offline List swipe feature is modeled after:
Hope this helps explain a bit of our thinking when planning the UI and user experience.