Excellent Crash Reports

I find that a majority of the crash reports that come in for ReceiptWallet have the following for the description:

 

Yes, they are blank! While I appreciate people sending in crash reports (I read everyone of them and try to figure out the problem), having no description makes it much harder to figure out the problem. Today I received a blank description, but in reading the report, I was able to “reproduce it” (hard to reproduce when I wasn’t told what happened) and quickly fixed it. I’m contemplating making description a required field for the report; this could reduce the reports which I don’t want as it would give me a false view of how many crashes people are getting.

Filtering NSTextField – Take 2

Thanks to Jim Correia of Bare Bones Software, I have a slightly different method for filtering NSTextFields based on an NSFormatter. While my older method worked, this is a bit cleaner.

Like my old filter, this also has three methods:

- (void) setAcceptableCharacterSet:(NSCharacterSet *) inCharacterSet;
- (void) setMaximumLength:(int) inLength;
- (void) setMaximumValue:(int) inValue;

However, they’re called differently. You’d do something like this:

NSMutableCharacterSet *characterSet = [[NSMutableCharacterSet alloc] init];
[characterSet addCharactersInString:@"0123456789"];
[secondaryTextField setFormatter:[[[PartialFormatter alloc] init] autorelease]];
[[secondaryTextField formatter] setMaximumValue:65535];
[[secondaryTextField formatter] setAcceptableCharacterSet:characterSet];
[characterSet release];

Note that the formatter is based on NSFormatter and not NSNumberFormatter. I actually am using this for a number field as I want the number field to give me back a string instead of a number, so that’s why I put in the setMaximumValue and didn’t base it on NSNumberFormatter.

As always, feedback is welcome.

The attached code can be freely used in commercial and non-commercial projects. While I’d like some credit in the about box, it isn’t necessary. This code has no warranty and you assume all risk for using it.

Download source

Easiest update to WordPress yet!

I saw that WordPress 2.5 was released and always dread updating my WordPress installations as I have to read the instructions so I don’t screw it up. Well, today I decided to try out the update script I wrote and I was amazed (OK, I shouldn’t have been amazed) that it took just a few seconds and the upgrade was done. Everything seemed to work and now I’m running WordPress 2.5 on 2 installations! I’m not sure what I get out of the new versions, but the admin interface looks cool. Thanks WordPress folks for the upgrade and if you upgrade your WordPress installation when new versions come out, definitely check out my script as it could save you a lot of time.

NSTextField’s lack of filter capabilities

I love Cocoa, but it seems that some simple things are missing. For example, NSTextField doesn’t have the ability to filter text input as the user is typing. A friend reminded me that this is a feature that PowerPlant had ages ago. Cocoa has NSFormatters which allow the field to be validated after text is input, but in many cases, the right way to restrict input is to prevent it from being typed. I like NSFormatters and have created a very complex one to handle multiple currencies in ReceiptWallet, but I realized I needed something else.

So, I present FilteringTextField. The attached code can be freely used in commercial and non-commercial projects. While I’d like some credit in the about box, it isn’t necessary. This code has no warranty and you assume all risk for using it.

The subclass of NSTextField, has 3 methods.

- (void) setAcceptableCharacterSet:(NSCharacterSet *) inCharacterSet;
- (void) setMaximumLength:(int) inLength;
- (void) setMaximumValue:(int) inValue;

The first lets you set the characters that can be typed; anything that isn’t in the set is eaten. The second, only allows x characters to be typed and the last limits the value if the user is typing in a number. This class can easily be extended to handle other constraints. Pasting in text is also filtered.

If anyone finds problems with this code, please let me know.

Download source

Cool Cheap Camcorder

Last Sunday, I saw on Richard Wanderman’s blog a note about David Pogue’s review of the Flip Ultra. Last year I was contemplating getting an HD video camera to record our son’s first year and eventually his first steps. I spent a long time researching and thinking about it. I was about to purchase one, but decided against it as it isn’t all that convenient to use any camcorder.

When I saw the Flip Ultra, I said cool. The resolution, 640×480 is four times the resolution of the video clips on our digital camera, so what did I have to lose in getting one. I ordered on Sunday from Amazon for about $142 and received it yesterday. It is so easy to use, it’s unbelievable. I’ve only taken a few clips with it, but I can see us using it a lot and hopefully we’ll always have it handy to record our son.

The only downside I see right now is that it uses the 3ivx codec. Why is that a problem? Well, if you want to playback the video, you have to install the codec and if we want to post video online, others have to also download the codec which isn’t all that easy for novices. However, since I have QuickTime Pro, I can export video to H.264 which pretty much everyone can view these days. (I realized today why they chose 3ivx; it has to do with money. The H.264 and AAC codecs could amount to several dollars per unit shipped and with the Flip Ultra costing $140, a few dollars can make a huge difference.)

I think that I’m going to be quite happy with this as the main purpose was to shoot better video than what our digital camera does and at the resolution it does, it easily meets that requirement.

Oh the irony

Today I was digging through some files in my file cabinet looking for my business tax certificate. I mentioned this to a friend and he said “You do realize the irony here, right?”. Yeah, I realize that I’ve written this awesome program for dealing with documents and here I am digging through paper. I do have a good reason for this. I like to keep my business and personal documents separate, so I never scanned in my business documents into DocumentWallet and didn’t scan my receipts into ReceiptWallet. Now that ReceiptWallet handles multiple libraries, separating business and personal is quite simple, so I’ve begun to put business documents into a separate ReceiptWallet document library.

Before ReceiptWallet 2.0, doing this was not very practical. While there have been some user rumblings about some of the ReceiptWallet 2.0 changes including multiple libraries, this experience shows me that the multiple library decision was definitely a correct one. It may take some time for users to get used to multiple libraries, but in the end, I think that users will find many uses for them.

Can’t buy reviews like this!

theappleblogcom20080326budgetorganizeanddeclutteryourlifewithreceiptwallet-clipped.pngA few friends of mine pointed me to a ReceiptWallet review today over at The Apple Blog. I had no idea that a review was being written and that it would be so glowing! While the user base of ReceiptWallet is increasing, I usually don’t hear from users unless they are having problems. Reading reviews like this makes me smile and know that all my hard work is appreciated.

Any other reviews out there? Let me know.

Buying a computer? Wait a week?

I’m not sure where I heard it, but I love the saying that says if you want to buy a computer, wait a week. There will never be a good time to buy technology as it will always get “better” and become cheaper. I had been planning on purchasing a new MacBook Pro after I paid my taxes, my my dog’s root canal put that on hold. Today, I’m sort of glad I waited and will be waiting for the new round of MacBook Pros to come out (whenever that is) because Fujitsu announced a 320 GB 7200 RPM portable drives. I always get my portable machines with 7200 RPM drives as I like the extra speed for development. As of now, the largest you can get (at least from Apple in a build to order configuration) is 200 GB for a 7200 RPM drive. Hopefully Apple makes the Fujitsu an option or other vendors increase capacity for the 7200 RPM drives.

Waiting, however, will be hard as my current machine is approaching 2 years old which is an eternity in computer time.

Another PDFKit bug

In my ongoing saga with PDFKit, a user had a crash that I couldn’t reproduce and generously sent me the PDF that caused the issue. I was immediately able to reproduce the problem and furthermore, managed to get Preview to crash on that PDF. The crash was occurring when I tried to generate the thumbnail for the PDF.

Here’s what doesn’t work on all PDFs:

PDFDocument *pdfDoc = [[PDFDocument alloc] initWithURL:[NSURL fileURLWithPath:fullPath]];
int thumbnailPage = [[self valueForKey:@"thumbnailpage"] intValue];
int pdfPageCount = [pdfDoc pageCount];
if (thumbnailPage < pdfPageCount && pdfPageCount > 0 && thumbnailPage >= 0)
{
	PDFPage *page = [pdfDoc pageAtIndex:thumbnailPage];
	if (page != nil)
	{
		NSData *data = [page dataRepresentation];
		if (data)
		{
			image = [[NSImage alloc] initWithData:data];
		}
	}
}

[pdfDoc release];

Here’s what works on all PDFs I’ve tested including the one in question:

NSPDFImageRep *pdfRep = [[NSPDFImageRep alloc] initWithData:
	[NSData dataWithContentsOfURL:[NSURL fileURLWithPath:fullPath]]];
if (pdfRep)
{
	int thumbnailPage = [[self valueForKey:@"thumbnailpage"] intValue];
	int pdfPageCount = [pdfRep pageCount];
	if (thumbnailPage < pdfPageCount && pdfPageCount >= 0 && thumbnailPage >= 0)
	{
		_DebugLog(@"thumbnail page count is valid");
		[pdfRep setCurrentPage:thumbnailPage];
		image = [[NSImage alloc] initWithSize:[pdfRep bounds].size];
		[image addRepresentation:pdfRep];
		[image setDataRetained:YES];
	}
	[pdfRep release];
}

So what does this tell me? It tells me that NSPDFImageRep handles PDFs better than PDFDocument/PDFPage does. I fixed that crash and optimized some other code while I was at it. This still doesn’t solve all my problems with PDFKit as the PDF in question crashes when I try to write metadata to it (it crashes Preview as well). Not much I can do about that, yet.

Update:Funny, when I put this code in a test application, it no longer crashes. I still believe something is wrong with PDFKit as the crash looks very suspicious:

Thread 0 Crashed:
0   libSystem.B.dylib             	0x93287474  
tiny_malloc_from_free_list +
548
1   libSystem.B.dylib             	0x93280ba8 szone_malloc + 200
2   com.apple.CoreFoundation      	0x92342414 __CFDictionaryGrow + 200
3   com.apple.CoreFoundation      	0x92342d64 CFDictionarySetValue + 252
4   libCGATS.A.dylib              	0x95265440  
get_name_with_name_code_nl + 532
5   libCGATS.A.dylib              	0x952654cc  
ats_name_handler_copy_full_name + 20
6   libCGATS.A.dylib              	0x95266ad0 copy_full_name + 36
7   com.apple.CoreGraphics        	0x919b1fd0 CGFontNameTableCreate +  
252
8   com.apple.CoreGraphics        	0x919b1e9c CGFontGetPostScriptName  
+ 36
9   libPDFRIP.A.dylib             	0x068fba64  
PDFFontType1EmitDefinition + 60
10  libPDFRIP.A.dylib             	0x068f8678 PDFFontEmitDefinitions +  
52
11  libPDFRIP.A.dylib             	0x068f9aa8 emitFontDefinition + 20
12  com.apple.CoreFoundation      	0x923743e0 CFSetApplyFunction + 284
13  libPDFRIP.A.dylib             	0x068f9b0c  
PDFFontSetEmitDefinitions + 68
14  libPDFRIP.A.dylib   
        	0x068f68e0 PDFDocumentFinalize + 312
15  libPDFRIP.A.dylib             	0x068f5314 pdf_Finalize + 24
16  com.apple.CoreGraphics        	0x919e5914  
CGContextDelegateFinalize + 72
17  com.apple.CoreFoundation      	0x92371840 _CFRelease + 216
18  com.apple.CoreGraphics        	0x919e58f4  
CGContextDelegateFinalize + 40
19  com.apple.PDFKit              	0x914f77d4 - 
[PDFPage(PDFPageInternal) writeToConsumer:] + 444
20  com.apple.PDFKit              	0x914f6a28 -[PDFPage  
dataRepresentation] + 84
21  ...gtenterprises.receiptwallet	0x0001b8dc -[ReceiptMO  
imageWithWritingThumbnail:] + 988

Defective dog

Our dog had his root canal yesterday performed by Dr. Brook Niemiec. Everything went as planned, except after the initial exam, the vet showed us that Marley had an extra, useless tooth that was encroaching on his front teeth. So, that tooth had to be removed which made the $2000 dog bone even more expensive. Other than Marley being on some drugs for a week and having to eat soft food for 2 weeks, he seems to be doing fine and will be back to his normal self soon. As Marley has been a part of our lives for 3 years, I was very worried about the procedure as he had to be anesthetized. This may be a routine procedure, but anesthesia scares me. I’ve asked for copies of the X-rays and once I get them, I’ll put them up. I figure that for what I paid to repair Marley’s teeth, I might as well let others look at the pictures.