Jump to content

rragan

Members
  • Posts

    1003
  • Joined

  • Last visited

  • Days Won

    75

Posts posted by rragan

  1. I don't know how Android functions with respect to the GPS but my observation on iOS is that you can collect samples for as long as you want and if the phone is not moving, the original GPS locating is reused -- saves battery. 

    I end up taking a reading, walking some distance away and back and take another reading. Repeat varying the direction you walk away. Averaging each separate reading is a pain so if one wanted to make it better, an averaging mode would guide you to walk away and back and put samples in a bucket that it would average when you tire of your drunkards walk. 

  2. Having logged a lot of caches at the Yuma Mega, I got to feeling tapped out. 

    Tap Log this cache

    Tap Log type

    Tap Found it

    Tap message

    How about from the log type screen making a long press go right to entering the message? This is almost always my flow and I suspect that of most folks  

     

  3. Once you have the final coordinates, add them as a waypoint and tap the Is Corrected Coordinate button. Save the waypoint. There will now be a red triangle on top of the cache icon so you can spot it. However, in Live view, the Geocaching.com API only returns caches based on published coordinates. You will still see the red triangle but only if the published Coords land in your search area. The displayed position will reflect the solved location. Offline lists always show the final Coords. I keep an offline list named "Solved" where I save all solved mystery caches. I can examine it and see what is in my Tour area easily. 

  4. I use offline lists to manage things like "Need to Sign", "Signed","Working On",...

    It would be handy to be able to see the lists a Cache belongs to as an action on the cache page. Removing a cache from a list like "Need To Sign" would be easy then vs switching to that list, finding the cache and deleting it from the list. Add to "Signed" list would use existing add to offline list. 

  5. Low priority but so useful

    Often when listing caches to meet a challenge, you need to supply gccode, title, date found or just gccode and name. A simple append mode switch would append each thing tapped to the clipboard with a space after. So append on tap,tap,tap and I'm off to paste the result. 

  6. Geocaching.com owns the coord.info and geocaching.com URLs and so can dictate what app opens to those. Of course, they choose their own app and Apple, unlike Android, does not let you change that setting. 

    The next best thing is to let it open in Safari and once on the cache page press the GPX button and choose Copy to Cachly 

  7. Any regex that has the first match part way into the string and not end with .* needs a .* at both ends. I just tried ^abc$  matching abc as the whole string. Adding .* to the start and the end and it still matched so this odd case that worried me is fine. 

    It looks like if it does not start with .* then add .* to the start. If it does not end with .*, add that to the end. I believe this action will make regex work like users expect it to. 

  8. 1 hour ago, barefootguru said:

    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.

    Or say, if you want your regex as written, it must start with ^ and end with $.  Then only add the .* when no ^$ is present. 

  9. Parsing this wording carefully

    "

    and all all the examples I can find makes it seem that in this context, anything other than a complete match will fail even if I'm using the regex to see if a particular substring is present which regex users from other languages do all the time. Users will need this explained clearly or they will be puzzled as I was. 

    I thought some about prepending .* to the start and end of the user regex. Since this matches zero or more, it might not cause a problem except if the regex has ^ and $ usage. It would magically make lots of things just work but regex's are so complex, I'm not sure there aren't edge cases this would mess up. 

×
×
  • Create New...