Jump to content

Ben H

Members
  • Posts

    299
  • Joined

  • Last visited

Everything posted by Ben H

  1. Cache notes will be in our 5.3 release, which should be available in several weeks.
  2. Looks like you've made an assumption. Had you asked rather than assuming, I would have answered that the bug you're referring to will also be fixed in the 5.2 release rolling out this week. Once fixed, tapping on the small map after clicking the link in an email will open the full map as expected.
  3. Our 5.2 release will be available next week and includes additional features around the Drafts workflow we introduced in 5.0. The 5.3 release will be a few weeks after that and will include a way to turn off the proximity alert (among other things).
  4. As long as you haven't changed the name of the list, re-sending the list should overwrite the old file. There is nothing random in the file names; the naming convention is -[unique list identifier]. The latter is a unique BM code for the list analogous to unique GC codes for caches.
  5. We're sorry that Garmin Express does not support some devices and operating systems. Unfortunately, which devices and operating systems are supported is out of our control. We do know that Garmin is working hard to offer support in Garmin Express that is as broad as possible. A fix will be released soon that was preventing the "Saved" confirmation from showing after caches are added to a list. As with the old method of adding to lists, the new methods do not add duplicate listings of a single cache to a list We wish we could fix the existing Send to GPS feature for single caches, but unfortunately that feature relies on browser plugins that are not longer supported by modern web browsers. (See the Garmin Communicator Plugin page or this article from Google for more info.) When we asked Garmin to partner with us on a replacement for the functionality that was previously delivered by the Garmin Communicator Plugin they decided that Garmin Express was the best option for their part. We hope that we can create an experience that is just as easy as what was possible with the Communicator Plugin.
  6. Can you explain more what is happening with your compass? Also, what version of the app and Android operating system are you using? Thanks!
  7. Thanks for reporting the problem. We are aware of this bug and have a fixed completed that will be in our next release. I expect that release will be available next week. Sorry for the inconvenience in the meantime.
  8. Hans - Could you confirm the source of your GPX file that does not show HTML encoding problems? We've been investigating and we're seeing the same bug (like your second screen grab) from all sources, including PQs and single cache GPX files.
  9. Hi Ben, The problem is that for all members to use Send to GPS (a fairly useful feature, by the way), they must reduce security measures by either using an old OS, an older browser, or manually enabling a class of plugins that developers are now actively trying to discourage using. Now there are workarounds, but they are really only useful to premium members. So for the casual geocacher that doesn't want to pay for premium membership, it's somewhat reckless and irresponsible to ask these users to compromise their security to play the game. The new workaround for lists is a partial solution and on the right track. But again, it's only available to premium members and it only really solves the "problem" of having to create a pocket query from a list. The same feature needs to be put directly onto cache pages to either replace Send to GPS, or put beside it. The other option you guys could implement is to allow basic members to directly download the lite GPX file - the same file created with the Send to GPS button - via the Download GPX button. Yes, basic members have access to LOC files, but those are useless as most GPS units don't recognize them, and converting them is a pain (see this thread about requesting that they be removed for this reason). Once again, we're not asking that you open up new features to basic members, just modify the existing ones to stay current with technology so that basic members aren't losing features that were once available to them. Be pro-active to trends rather than reactive. Implement a permanent replacement for Send to GPS before the communicator plugins are completely unuseable. Thank you, Mineral2 Thanks for the thoughtful response. My previous post in this thread was not meant to say that we won't update Send to GPS, but rather to dispel the claim that yesterday's Send to Garmin release had actively removed functionality for basic members. That claim simply was not true. We know that we have more work to do to support GPS users - including basic members - in getting content to their devices. The biggest challenge in delivering a feature like Send to GPS or Send to Garmin is that it absolutely requires collaboration with the device manufacturer. I and many others worked with multiple teams at Garmin for more than a year to make the Garmin Express integration a reality. Unfortunately there is nothing quick and easy about it. Yesterday's release was never intended to be a complete solution for getting content to GPS units. I posted some more thoughts about what comes next in yesterday's release notes thread. I'd prefer to keep most of that conversation over there if you have more feedback. Thanks!
  10. You can access your watchlist and favorites from the right sidebar of your dashboard page. You'll find Lists about midway down, just below Premium Features.
  11. Thanks for the additional details. We'll look into the encoding and header issues and fix them soon.
  12. Thanks for reporting this. We have the bug tracked and hope to fix it as soon as possible.
  13. I was finally correct (I would have wished to be wrong however). http://forums.Groundspeak.com/GC/index.php?showtopic=343784 Actually it is even worse than what I guessed would happen as basic members cannot even transfer the waypoints of traditionals via this new method as they cannot use lists. Actually, you're completely wrong. Today's release changed nothing about what basic members are able to do. All previously existing Send to GPS and other file download options that were available yesterday are still available today.
  14. Thanks for the feedback, everyone. I'd like to be clear that today's release was completely additive by design. We have not yet replaced any previously existing functionality, nor did we remove any existing features for basic members. Any basic or premium member who was using existing Send to GPS functionality or file downloads yesterday will find those in exactly the same spots today. Today's release was only about making Lists - a premium member tool - more powerful for premium members by providing downloads on demand. That said, this collaboration with Garmin is indeed something that could make its way to other areas of geocaching.com. As you all know, although Send to GPS is still functional it has been slowly eroding for several years. For most users Send to GPS is a broken experience and we'd like to fix that. With that in mind we'll be watching feedback to learn whether the Send to Garmin workflow proves valuable to players so that we can decide whether it should be implemented elsewhere. If we do reach the point where we consider replacing the any of the current download options, we know that we'll need to re-visit how to support basic members and players with non-Garmin GPS units. To summarize: today's release was a start. We'll be watching usage data and feedback to determine what comes next.
  15. I was wondering if GS had and views on this post? Hi there. Thanks for the feedback. We tested some early prototypes of this feature where caches with a found it draft were shown as smileys. Unfortunately, doing that ended up confusing more users than it helped. That said, we know that as you've mentioned it's important to know which caches you've finished for now once you've creatied a draft for them. For that reason, our next release will include an update to show a different map pin for caches which you've saved a draft for. Hopefully that will address the situation you've described. Hi Ben I really appreciate your reply, but I feel very strongly that you need to also have a different icon in the lists. Maps are not the only place that seeing the smiley is important and key to the usability of the drafts. I really would urge you to re-consider your decision, I can understand why people could get confused if the smiley was the exactly the same although not entirely, if you have found a cache you have found a cache at the end of the day. A smiley isn't to say that you have logged it, but knowing it was in draft still would be of benefit. How about a smiley with that little mustard colored dot that is starting to appear in various places now, if that was perhaps somehow incorporated, or perhaps a slightly lighter shaded yellow that kind of thing. I thought drafts was brilliant other than missing this important feature. I hope that you are able to incorporate this request going forward. I neglected to mention that caches with drafts will also be badged in list views starting in the next release.
  16. I was wondering if GS had and views on this post? Hi there. Thanks for the feedback. We tested some early prototypes of this feature where caches with a found it draft were shown as smileys. Unfortunately, doing that ended up confusing more users than it helped. That said, we know that as you've mentioned it's important to know which caches you've finished for now once you've creatied a draft for them. For that reason, our next release will include an update to show a different map pin for caches which you've saved a draft for. Hopefully that will address the situation you've described.
  17. Hi there. There's currently a bug on the Android app where the attended log option is not displaying correctly. This will be fixed in our next release. Sorry for the inconvenience.
  18. Hi there, We added cache owner log types in our 5.1 update, which was released last week. You should see these options if you've updated to the most recent version.
  19. Also, once you reach the screen that says you have no drafts, could you please try pulling down to refresh the list? It's possible that you encountered a temporary hiccup that could be resolved by forcing a manual refresh.
  20. Thanks for reporting the problem. Any chance you can provide more details about how you got into the state you're seeing? A list of steps - how you created the drafts, whether you were offline at any point, whether any drafts were created outside the app, etc - could help us in tracking down the issue.
  21. Thanks for the feedback. We'll look into better attribution for OSM data. We're required to display the Google logo because we're using Google's framework for displaying all maps, including those based on OSM data.
  22. Thanks for the kind words and the amusing video. Hi Beechtrees. You may need to update your Android OS in order to update to the newest version of our app. Currently, you need to have Android version 4.4 (KitKat) or later to use our latest releases. Version 4.4.1 of our app - the version you have - is the last version we released that supported Android versions 4.1-4.3.1 (Jelly Bean). Please let us know if you do have Android 4.4 or later and you're still unable to update the Geocaching app.
  23. Thanks for the feedback, everyone. We're looking at options for improving this for more experienced users in the next couple months.
  24. It could actually be quite helpful of you'd report a bit more info. I'm most interested to know whether it happens every time you open and email or just sometimes. If only sometimes, it would be great to know the details of those times. Thanks!
×
×
  • Create New...