Time Machine saved me again!

I'm quite religious about my backups, but luckily haven't had to use them except for a whole hard drive failure several years back. However, today, QuickBooks 2007 for the Mac ate my data file and required me to use Time Machine again. I lost 1 invoice and 1 payment which I just entered, so restoring wasn't bad. This is twice in 1 week that I've had to use Time Machine. I'm glad it is there, but am a bit nervous that I've had such bad luck this week.

Furthermore, QuickBooks has some problems with Cocoa bindings as demonstrated by an error in the console log:

2/2/08 7:03:18 PM QuickBooks 2007[36756] An instance 0x17820a30 of class QBCompanyFileDoc is being deallocated while key value observers are still registered with it. Observation info is being leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
(
Context: 0x148b42a0, Property: 0x179987a0>
)

I ran into this the other day with ReceiptWallet, but using my binding debug object, I was able to solve it. I guess Leopard got more strict on things like this and is now logging errors. Will Intuit fix this and make QuickBooks more stable? There was recently reported a huge data loss issue with the product which I didn't think affected me. I hope this isn't another data loss issue. Of course, I can't reproduce it (nor would I want to), so reporting it to Intuit is probably useless.

Do I ask for too much?

For my latest beta version of ReceiptWallet, I've specifically disabled the auto update mechanism by putting in a bogus link in the Sparkle feed for the actual update. Instead, in the text of the dialog, I tell people that clicking the Install Update button will fail, to read the text, and then have the real link in the text. I've done this on purpose as the new beta has some major changes and I really, really want people to back up their data before installing. If they can't install the update, then their data can't get hosed. This seems to be working. So far I've had 3 reports that people couldn't install the update. This means that they didn't read the text and just hit "Install Update". Furthermore, whatever text I put in the dialog, no matter how large, it won't be read. I even made the text real large as shown below. Even in the smallest window size, I think the large text would get people's attention and then maybe they'd scroll down.

Hmmm. Is there any use in putting text in the update dialog if people just hit Install Update? Maybe not. It's cool that I can put whatever I want in the dialog, but maybe all I need (for normal updates) is "See our website for information about this update."

Should I abandon my over zealousness for caution and just let people install the update without reading? If I do, there could be data loss. If I don't, the chances of people testing will decrease.

ReceiptWallet 1.6.0 b2 Ready to Go

I'm extremely pleased to say that ReceiptWallet 1.6.0 b2 (and DocumentWallet 1.2.0 b2) are now ready for testing (b1 had 2 bugs in it). This version brings a huge change to the product in that you now can have more than 1 library. For users that don't want more than 1 library, there will be few changes.

While the changes on the surface may look minor, I think it will bring a huge amount of flexibility to the products. People have been asking for the ability to start fresh with the new year. The multiple libraries feature will make that a reality. Each Library is actually a file package that contains the main database as well as folders for the receipts and thumbnails. Furthermore, you can copy the libraries onto a read only volume or burn to a CD and then be able to open up the library simply by double clicking.

I have gone to great lengths to ensure that everything works, but I'm sure I missed stuff. I've done most of my testing on Leopard, but done basic testing on Tiger.

If you want to give it a whirl, make sure you have the latest released version of the product, go into Preferences and change the Look for popup (in the lower right) to be Beta versions and Releases and then do a Check for Updates. When it says that there is an update, read the text CAREFULLY. You'll have to click a link to download the beta; clicking Installing Update will fail as I want people to read. So far, the 2 people that I have had try the new version, failed to read the text which says to backup, so I think this is wise for now; a bit inconvenient, but better than losing data.

Feel free to send me feedback. I have a few more tricks up my sleeve, but they'll wait for the next release.

UI Feedback needed

I've spent a significant amount of time working on the new version of ReceiptWallet. One of the changes is that information about a Library is now in a floating panel. However, I'm not happy with the buttons/look of the panel. I'm looking for ideas that people may have. Please feel free to post comments on send me email with ideas. Thanks!

Here's what it looks like: