BethKatzPA

I've brought this up in the Facebook group, but I thought mentioning it here would be more appropriate. Thank you, Nic, for addressing some of my dark mode concerns on Facebook. Despite some people not liking it, some people do. It's not going away. Some color choices do not work well in dark mode. I was using HTML-purple for some text. It was almost unreadable. I changed it to HTML-mediumpurple, and that was much better. A bigger concern is that inks seem to be rendered in HTML-blue even in dark mode. That it too saturated to be readable in dark mode. I found that HTML-royalblue works okay and could be used for both light and dark mode. HTML-dodgerblue is even better for links. Thank you.

Okay.

A friend and I are both using Cachly 5. He created a list for an upcoming adventure. He sent it to me as a text message. I saved it to Dropbox and imported it into a new offline list in Cachly. When I opened the list, I was surprised to see a smile for a find. The cache said I had found it (but not a date). I took a screenshot. By pulling down on the cache to force it to update, the smile and find went away.

When I complete geo-art, it would be nice to have the found caches go back to their posted coordinates that make the picture. I understand that some people want the cache finds to show where they were found. Could we please have a toggle to indicate whether we want a find to display at its posted coords or its solved coords? It should be on a cache-by-cache basis.

I just checked this in 4.3. It's still broken. No, I hadn't reported it previously. I'm usually out in the field when I run into it. And then I figure I am doing something wrong. I create a waypoint and set it as a target. But then after using it, I decide the coords aren't as good as they could be. So I choose Edit waypoint and save. The waypoint is no longer the target. However, if I tap on it, I don't have the option to make it the target. I have to tap on some other waypoint, make that the target, and then tap on the one I am working on and make it the target again. I can repeat this sitting at home as well as out in the field.

I'm not quite sure how to reproduce this, but the find count included in the two logs after I logged a Needs Maintenance was one too many. The NM was not intended to be a find. I'm thinking that the NM counted as a find within Cachly. I did a separate found and saved as a draft. It was one of the ones that was one high. I use a text template that included my find count.

I have final coords for some mysteries in a text file. I didn't include the N and W because I'm lazy and they are extra characters. So I copied and pasted one into a waypoint title. Tapping on the latitude field updated the coords. I LOVE HOW THAT WORKS! However, I didn't notice that the longitude chose E instead of W. I was confused when I went to the map because the coords for final should have been close. It took me a moment to realize what had happened and switch the E to W and get it to save. I propose that pasted coords that don't have N-S or E-W default to either the current location's quadrant or the cache's quadrant. I don't care which. People living closer to the edges might have a preference. By the way, I'd like an option to display cache at both posted and corrected coordinates. I'd like to see my geo-art as the art but also know where the caches are along the trail. Thank you.

Geocaching recently introduced a coordinate checker for mysteries. I was surprised that it does not display in Cachly or the official app. I gather they do not allow access to it from the API? I was very disappointed. We published geo-art, and the checkers only show on the web site. I know we can use third-party coordinate checkers.

Emailed.

I used Cachly to create a bunch of waypoints on a cache and want to share them with a friend as points of interest on a hike. I thought I could export a GPX file and share it with him, but the waypoints aren't imported. They are in the GPX file if I look at it in TextEdit. But if I import it into another offline list, only one waypoint shows up.

Yes. The pin moves when I have corrected coordinates. It would be really nice to be able to display both posted and corrected coordinates especially for geo-art.

I'm caching in a valley that has multiple multi-stage caches. I've found them all but would like to hike the area again and perhaps add a cache of my own. I'd like to be able to look at the overview map with radius circles and see all of the stages. Now, if I display corrected coordinates, the first stage doesn't show. In addition, I'd like to be able to have a toggle to show both posted and corrected coordinates. This would let me see geo-art as art as well as searchable containers. That could be an overall setting or an individual cache setting.

Plus I just noticed that I did one twice. And I didn't even mention the Earthcache at the beginning. Oh well. Thank you for a great app. I'm really enjoying it.

Okay. I'm trying to balance keeping the finds in order, storing the information off my phone, writing good logs, and making sure I log trackables that have changed status (picked up or dropped off) as quickly as possible. I guess those goals aren't compatible.

I think there is a bug with the log template, find_count variable, and drafts. My default log text to be filled in when I'm on my computer is # *|find_count|*. TFTC I've been saving as draft and sending immediately. Today, I had decent cel service while caching and just did a find, send as draft, and send now. The screenshot from the draft page online shows the caches I found in the correct order with newest on top. I have completed logs on 2105 caches. So the first log for today (at the bottom) has the correct find number of #2106. However, it was raining, and before the fifth cache, I had to reboot my phone. Apparently Cachly did not have the info that I had sent four previous cache finds as drafts. The topmost cache also has #2106 as its find number. In addition, sitting at home, if I go to a cache listing, start to log it, preview the log, it also says that it will be #2106. I thought the find count used to work flawlessly.