Version 4.6 Released

Last week version 4.6 was released. This version is a pretty minor release after the big feature 4.5 version. Albeit this new version adds some handy interface elements. We added Folder and Geocache menus to the main menu for commonly used functionality. We also added the ability to collapse parts of the main window, like the listpane to the left and the tabs pane at the bottom. Perfect for users with a smaller screen. Tip: take a look at the keyboard shortcuts!

There are also multiple bugs solved. Most important ones: timezone issues with logging of caches and crashes on import (some users experienced this, but unfortunately not reproducable on our development machines).

Today we send version 4.65 to Apple for review, to solve some more bugs. In version 4.6 we introduced an issue that the Map jumps to the home location every time the Map is activated. There was also an issue with photo’s sticking to multiple logs. Both will be solved.

The mysterious mystery of disappearing mysteries

That’s a kind of nice title, isn’t it? 🙂

Last week IDisappearingMystery began to receive mails from users ‘complaining’ that iCaching doesn’t recognize ‘Mystery’ caches as such. One user also dived into the GPX-files and discovered that Groundspeak, all of a sudden, has decided to rename the <type>-tag from “Geocache|Unknown Cache” to “Geocache|Mystery Cache”. To make things even worse, they already had a naming inconsistency between GPX-files and de API, where the latter called these “Unknown (Mystery) Cache”.

Although the new name is like we geocachers call this cachetype, I can’t apprecate the renaming-fever at Groundspeaks headquarter. Two weeks ago I discovered myself that they also renamed the additional waypoint-type “Stage of a multicache” into “Physical waypoint”, and “Question to answer” into “Virtual waypoint”. This renaming breaks compatibility with applications like iCaching, but also with the cachetypes on your paperless GPS-devices.

The workaround at the moment is to update the caches through the API instead of GPX-files. We’ll make iCaching recognize the new names from the next update. On the export-side of iCaching we’ll keep the old names. This way, your GPS will still recognize the correct cache- and waypoint types.

Version 4.5 is in the Mac App Store now

From now on you can log your finds (or didn’t finds) directly from iCaching. Even including photos. This was one of the most asked features.

You can import the fieldnotes from your GPS, or select caches from your database to log them.

iCaching keeps track of your number of finds, you can reorder the logs by drag and drop.

Spread the word and Happy Caching The log list Editing a log

New: like us on Facebook

Recently we introduced an iCaching Facebook page. This is a nice way to interact with our users.

So visit our page and like us!

Update website

We had some trouble with the hosting of our website, so we had to re-setup the site. While doing this, we saw room for improvement, so the site has a new structure: the main features are listed on the homepage now and there is one support page for the faq and contact form.

We hope this gives a better impression of iCaching.


Tips and tricks: using filters

iCaching has a pretty powerfull filtering mechanism. You can do a single filter action by pressing the magnifier icon in the toolbar, but you can also save a filter as a so called ‘Smart Folder’.

The filter dialog uses a standard Apple interface element to create the filters, but apparently not all users are familiair with this. One of the most frequent questions for support is how to create a ‘negative’ filter. E.g. search for all caches not owned by me.  Therefore this little post to give some insight.

You can create a search based on one or multiple filters. For most properties of the geocaches there is a filter. Clicking on a ‘+’-button adds a new filter.

The real fun part begins when you add so called ‘compound filters’. There are three compound filters:

  • ‘none’, you can use this for a negative filter: all rules nested must be not true
  • ‘all’: all of the nested filters must be true
  • ‘some’: it’s enough when just one of the nested filters is true

You can add a compound filter by clicking on a ‘+’-button while holding the alt (or option) key. You can drag filters around to organize the ordering of the filters.

Tips for faster filters:

  • Start with the most discriminating filters, this way the filter function has less comparisons left for the second filter etc..
  • Also important for speed is the processing cost of a filter; a boolean comparision (eg. Available=Yes) is cheaper than a nummeric comparision, which is cheaper than a text-comparision.
  • Within text comparisions (e.g. woner, cachename etc) a ‘begins with’ filter on a textbase property is cheaper than the ‘contains’ filter, because the filter only has to look at the first characters instead of the whole text
  • And last but not least: filtering on cacheproperties is (much) faster than filtering on it’s collections: additional waypoints, logs and attributes.

Here is a screendump of the Smart Folder I use myself to fill my GPS:


Just re-uploaded version 4.4

After a three week struggle with a technical issue concerning App Store approval, I just resubmitted version 4.4 for review. So when the guys of the review team don’t have another surprise, this update can be available soon.

This release is mainly a bugfix release. We managed to solve a bug in the importroutines for fetching pocketqueries through the API.

As a little surprise, we added OpenStreetMap and OpenCycleMap support to the Map window. For this version there is no visible user interface yet to use these maptypes, but by pressing ‘o’ (for OSM) or ‘p’ (for SCM) you can use these.

By the way, did you know that you can already use the keyboard shortcuts ‘r’ (roadmap), ‘s’ (satellite), ‘t’ (terrain), ‘u’ (satellite + roads) in the current version for switching maptypes?