NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
- Subject: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
- From: Todd Blanchard <email@hidden>
- Date: Sat, 23 Aug 2008 09:26:20 -0700
I have a document based app that does the right thing under Tiger.
Works great.
Under Leopard, NSApplication _doOpenUntitled is raising [NSCFArray
objectAtIndex:]: index (0) beyond bounds (0)
during the application opening sequence. There isn't a single routine
that is mine on the stack. So what array is _doOpenUntitled trying to
iterate on Leopard that it didn't on Tiger?
More clues:
I have a custom DocumentController that overrides newDocument: as
- (IBAction)newDocument:(id)sender
{
[self closeAllDocumentsWithDelegate:self
didCloseAllSelector
:@selector(documentController:didCloseAll:contextInfo:) contextInfo:0];
[super newDocument: sender];
}
because I only support one document open at a time. Oddly enough, if
I ignore the exception, this gets called twice during the opening
sequence on Leopard.
Anybody know what changed about the opening sequence or why this
should stop working on Leopard?
-Todd Blanchard
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden