• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger


  • Subject: Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
  • From: Todd Blanchard <email@hidden>
  • Date: Sat, 23 Aug 2008 13:40:59 -0700

I found it. CoreAudio being flakey again while being initialized. Changed order of initialization a bit and it stopped giving me the "no such property" error. It is different in Tiger and Leopard despite sticking to the 10.4 api.

Is it me or is the debugger becoming progressively more useless? I often find that it can't show me variables in the current scope and setting a breakpoint on NSException raise doesn't really reveal the point of error like it used to (lots of stack frames are omitted - even when they're mine).

Anyhow, thanks for noticing me.
-Todd Blanchard


On Aug 23, 2008, at 10:08 AM, Bill Bumgarner wrote:

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


_______________________________________________

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


  • Follow-Ups:
    • Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
      • From: "Kyle Sluder" <email@hidden>
References: 
 >NSApplication _doOpenUntitled raises exception under Leopard, not Tiger (From: Todd Blanchard <email@hidden>)
 >Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger (From: Bill Bumgarner <email@hidden>)

  • Prev by Date: Re: Implementing isEqual: and hash
  • Next by Date: Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
  • Previous by thread: Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
  • Next by thread: Re: NSApplication _doOpenUntitled raises exception under Leopard, not Tiger
  • Index(es):
    • Date
    • Thread