site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com On Sep 30, 2005, at 8:08 PM, Nick Zitzmann wrote: On Sep 30, 2005, at 4:57 PM, Ben Borofka wrote: [...] sherm-- Cocoa programming in Perl: http://camelbones.sourceforge.net Hire me! My resume: http://www.dot-app.org _______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.apple... Thread 0 Crashed: 0 com.apple.Foundation 0x970dc318 _NSRaiseError + 0xf8 1 com.apple.Foundation 0x970dc1fc +[NSException raise:format:] + 0x2c 2 com.apple.Foundation 0x9708eee0 -[NSPlaceholderString initWithString:] + 0x68 3 edu.csuchico.Passgen 0x00006e8c -[ComputerInfo init] + 0x6d4 4 com.apple.AppKit 0x92f6b878 -[NSCustomObject nibInstantiate] + 0x10c Check that -[ComputerInfo init] method. That's coming from your program, and it's apparently trying to call -[NSString initWithString:] with a nil argument. Ben, I noticed that you're calling -init from inside of nibInstantiate. Are you be trying to initialize something with the string value of an outlet? If so, that would be better deferred until -awakeFromNib. Doing so in -init *might* work, depending on whether the outlet has been initialized or not before your -init gets called, but it's not something you can rely on, since the order in which objects are initialized is neither defined nor guaranteed. -awakeFromNib is called after everything has been initialized; it's express purpose is to allow you to do any sort of initialization that depends on other objects in the nib. This email sent to site_archiver@lists.apple.com