Nic Hubbard

10 hours ago, DavSteph42 said:

Yes it that i want say ;-) Seeing immediatly the 5 last green or red dots.

Thanks!

This is something that we have on our feature list to add, but not sure when it will make it in.

Got it. I think this would be a nice feature addition.

When Cachly loads caches as search results, it loads "Lite" caches. In order to show the 5 dots we would we would have to load "Full" caches which would use part of your 6000 full caches per 24 hour limit that is imposed by geocaching.com. (Users can load 10,000 Lite caches per 24/hours)

We have considered using a Settings option to allow users to do this, but it hasn't been planned yet.

10 hours ago, AnyMules said:

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.

Glad it is working so well for you. We will be submitting 2.0.2 to Apple today.

I totally agree. However the API does not provide this info, so there isn't currently a way to do this.

16 hours ago, ElectroQTed said:

Wonderful! Thanks Nic.

The issue I was having, was adding text ahead of the default log, which I use at the end of all my "Found it" logs. When I tap "Log this Cache" and then "Message", the cursor is at the end of the default log. I want to add the body of my log ahead of this. I have to touch somewhere in the text of the default log and then slide my finger to the beginning of the default log to reposition the cursor. I find this cumbersome to do every time I log a cache. I also tried tapping at the beginning of the default log to reposition the cursor, but about half the time it would take me back to the previous screen because it is so close to the back arrow at the top of the screen.

It shouldn't be too hard to automatically make the cursor start at the beginning of the text, so I will fix this.

This is a feature that has been on our list for a while now. Just have not had a chance to add it. Hopefully in 2.1.

Can you explain the issue you were having with the default log text in Cachly?

This is an issue that was fixed in 2.0.2 which we will be submitting to Apple this week. Stay tuned. 

1 hour ago, ElectroQTed said:

Using Cachly on the trail for the first time today, I encountered issues with sorting the offline caches by distance. I was on a rail trail doing part of a power trail. As I walked from cache to cache, I went to the List View and re-sorted by distance. Sometimes the closest cache was at the top of the list, but mostly it was a mix of nearby caches. The only way I could get it to sort accurately, was to close the app, reopen it, and sort again. 

This is something that we are working on fixing. Basically we need to be updating the entire list for each GPS update we get. However, if it is a massive list this might have some performance ramifications, so we are working through this. 

35 minutes ago, ZeppelinDT said:

Huh.  That's weird.  I wonder why that is.  Although, now that you mention it, there was a recent event that was archived near me but it still shows up on the OFFICIAL app, which is definitely not supposed to happen.  So I wonder if that's an issue generated on Groundspeak's end with the way they archive certain caches.  (I noticed that the one archived event near me that kept showing up was archived by HQ, rather than by a local Admin or the Event creator... I wonder if that's somehow relevant).

I think the API has always worked this way. There is an option when we request caches to return caches that are archived or not. So I think it is intentional. 

2 hours ago, ZeppelinDT said:

So I'm still fairly new to this app but I've been playing around with it over the last few days and I noticed that one of the filter options in the live search is "Exclude Archived".  This has me a bit confused though, as I can't quite figure out its purpose - aren't archived caches always excluded from live searching?  I guess it doesn't hurt having it there, but I'm just wondering if this option serves some function that I'm just overlooking (e.g., is there a way to actually include archived caches in live search?)

Some event caches will still show up even though they are Archived. This is the real reason for this feature, was to hide those.

2 hours ago, barefootguru said:

It's not high on my list, but would be nice to see at least **bold** & *italic* Markdown displayed as bold & italic in log entries.

https://support.groundspeak.com/index.php?pg=kb.page&id=739

This is actually something we introduced way back in 1.0.4, but the overhead of converting logs with markup to attributed text was causing some performance issues. After that, we determined that few logs even use Markup, so we removed the feature and kept it on our feature list to fix the performance issues and add it again in a future version.

1 hour ago, Høst said:

When saving logs or field notes for later. Can it be done to choose "send all" when coming home? It takes som time to send 1 at the time when sending 20+ field notes 

Yes, this is a feature that we have been working on. However it isn't a quick and simple thing to add. Here is what has to happen with this feature:

1. Upload pending logs, one at a time to the server.
2. If pending log has a trackable to log, log each trackable one at a time.
3. If pending log has images to upload, upload images one at a time.

So there are quite a few working pieces to this feature. That being said, we are still actively working on it.

This is something that I have wanted to add for a while, so I made sure that I added it in for 2.0.2.

12 hours ago, Team DEMP said:

Today I found 2 caches that were muggled & I previously DNFed. I'm using the latest 2.0.2 beta with offline map. When I logged both as finds, the DNF icon also displayed with the smiley. 

Thanks for reporting this extra detail. Will test this today. 

This is a great feature request, and something I have wanted to add for a while.

Yes, as stated the 2.0.2 update will include this fix. We have to wait until to the New Year to submit the update to Apple since they are closed for the holiday.

Are you able to replicate the bug?

Glad that fixed it. We will squash that bug in the next update. 

This is a bug with the map type. Just change the map type on the main Live screen and this will fix your issue. 

We are looking into why the crash occurs. 

Can you tell me what map type you were using that was causing the crash?

4 hours ago, ZeppelinDT said:

Letterboxes are not necessarily at the given location.  A "true" letterbox usually requires following some set of instructions to find the final cache location.  A letterbox hybrid can be set up either like a traditional geocache (where its hidden at the given location) or it can be set up like a traditional letterbox (where its NOT hidden at the given location).  You can't really tell which way any given letterbox is hidden without reading the description.

Thanks for the input. I think we will keep it as is.

I will make sure to get this added in our next version.

1 hour ago, Bolling said:

Here's a suggestion. Instead of changing the color replace the circle with the Wherigo arrow. I know the theme would be different, but of course you can't capture a Wherigo cache from Cachly anyway. 

Of course there may also be legal issues with that approach. 

Yes, legally I would need to get permission to use it. 

Will add it to the list, however I will have to make it low priority as there are many other large features that need attention. 

Thanks for the suggestions. We do have the "multiple default log text" feature on our list, so it will get added sometime in the future.