Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
- Subject: Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
- From: Bill Bumgarner <email@hidden>
- Date: Sat, 23 Aug 2008 10:08:21 -0700
On Aug 23, 2008, at 9:26 AM, Todd Blanchard wrote:
- (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?
No idea, but it seems really odd to be closing all other documents
when a new document is being opened.
It sounds like what might be happening is:
- app launches
- app requests untitled document
- untitled document is opened
- newDocument: is invoked
- newDocument: closes the freshly opened untitled document
- something a-splodes in super's newDocument: because it was doing
something funky w/the untitled document
Do you need an untitled document? If not, kill it.
Otherwise, I'd need more context to understand the issue.
- what is the backtrace when the exception is tossed?
- what are the backtraces when -newDocument: is invoked twice?
... etc ...
b.bum
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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