CacheSense 3.1 Released
For those with Blackberry’s and using CacheSense (nee CacheBerry), or who are yet to make the smart move and convert, there is a new release available. CacheSense 3.1 is out and I have been fortunate to have had access to the beta releases over the last few weeks. There are lots of excellent changes that make this piece of software even better than before. From the release notes:
1. Facebook integration. New feature allows you to automatically update your Facebook status using Found, DNF or generic templates (just like the Twitter function). You need to authorize CacheSense (one time) via the Authorize button, this process is browser-based, secure and does not reveal your Facebook password to CacheSense. (Options | Facebook).
This is excellent and a great way to introduce others to your cache finds.
2. New “Update Facebook” function on the field notes screen menu. This feature lets you post a single Facebook status update with an associated comment that combines all geocaching activity since a given date (in a similar manner to the email/export field notes functions). Option to include DNFs. Option to include full field note text or just the template text.
3. Added “Notify on failure” options to Twitter and Facebook, if enabled you will be notified and given the option to retry if an update to either service fails for any reason. (Options | Facebook and Options |Twitter).
Always nice to know when you’re not going to be the centre of attention due to service failure!
4. Added new code to handle Internet connections, new Internet options allow you to select “Auto” or to specify a connection type. This change means CacheSense will choose the best (least cost) connection available rather than forcing the Direct TCP/IP (APN) mode. (Options | Internet).
Possibly the best code addition Bruce (the supreme genius who writes the software – a fine North Canterbury chap) has made. This has solved numerous issues CacheSense users have had with data communication. For me it has meant the ability to use the Twitter function that lay idle previously.
5. OS 5.0 and OS 6.0, CacheSense now uses the improved GPS API introduced in OS 5.0, this should result in generally quicker fixes and possibly better battery life. While the new API seems to work very well for most users there is a new GPS option to revert to the old code in case of problems. (Options | GPS).
I tested this out on a recent caching road trip and certainly seemed to have improved battery life.
6. New improved GPS fix dialogs (used for location sort, add waypoint and nearest caches). OS 4.2 thru OS 4.7 has same functionality but improved visually. OS 5.0+ displays real-time individual satellite position and signal quality.
7. Added Waypoint Projection to manual coordinate entry dialog.
Possibly the second best feature added in this release. No more needing to try and look up the Great Circle Calculator in your Blackberry browser out in the field.
8. Added State/Province column for summary and column views.
9. German Translation. Thanks to the hard work of user Jonny-blue, CacheSense is now available in German (will switch automatically based on your phone’s language settings).
10. Fixed ArrayIndexOutOfBoundsException when adding a child waypoint (caused by having other child waypoints with short names).
11. Fixed blank or partial screen when refreshing (or clearing tags etc) while the cache list is scrolled beyond the first screen.
12. Fixed empty cache list when sorting by GPS location and clicking OK before fix obtained.
13. Fixed filtering on GSAK User Sort (was treating as Boolean rather than an integer value).
14. Fixed filtering on GSAK User Flag.
15. Fixed failed or partial upload of field notes to geocaching.com. Caused by code exporting Memos as field notes.
16. Fixed failure when editing some existing custom filters.
17. Fixed refresh of child waypoint list after adding new child waypoint.
18. Fixed row height issues in summary and nearest cache views. Increased font size in nearest cache list.
And a whole bunch of other things I don’t really understand. 😉