Yes, the problem with the end of year issue is that the Cobalt will see that the current time is set to before the end of the last dive. If it sees that, it assumes the date is set improperly, and defaults to the most conservative option, which is to assume a zero surface interval after the last dive in the log. In one sense, it worked properly to maximize safety- but at the cost of massive irritation that should not occur in this sort of product.
Us not delivering the updated firmware- which has been ready more than a year- before the year rolled over is inexcusable, so I won't try. It comes down to human error. Partly in that we had "fixed" it so long ago that we didn't notice the fix was not out in the field as we dealt with adding new features. If we had been more on top of this we would have been clamoring for Atomic to get the firmware update posted well before the end of the year. All we can do at this point is apologize, keep working to improve the product, and do better in the future.
We do now have a fully functional Mac firmware updater at
Atomic Aquatics Cobalt Software, one that is very clean and efficient. The first company Atomic contracted with to do this (we just aren't desktop developers) failed to deliver anything, but used up a lot of time. The problem wasn't that the program worked on a predictable set of new Macs (that we could have released), it was that on some percentage of Lion/ ML systems, it would "brick" the Cobalt- and we couldn't tell which ones they would be in advance. The new program was written by the same folks that do Dive Log Manager, and it's great.
More user interface options, including a "Tech" or "expert" mode, silencing alarms, and more mixes are definitely in the cards for the wrist version/ Cobalt II and future updates. It's still an evolving platform, and we are paying attention to what users say.
Ron