NSPanel, DO & applications vs. bundles
NSPanel, DO & applications vs. bundles
- Subject: NSPanel, DO & applications vs. bundles
- From: Brad Peterson <email@hidden>
- Date: Wed, 21 Sep 2005 00:44:01 -0700 (PDT)
Hi all,
I'm stumped and hoping someone else has already
wrestled with this one...
I've got a sheet (NSPanel) which my main app can
display either by launching a separate app or through
a framework. In either case, the code displaying the
sheet is the same, and it displays the panel using
NSApp beginSheet: modalForWindow: modalDelegate:
didEndSelector: contextInfo:.
The code displaying the sheet finds the main app's
window through a DO protocol and passes that in as the
modalForWindow: value.
So far so good? (I know, it's unusual, but... I have
my reasons. Really, I do. ;) )
Here's where it gets odd. If the panel is displayed
via the main app calling into the framework directly,
the sheet pops out perfectly, and looks great.
If the panel is displayed via the main app launching a
separate app instead, the panel displays momentarily
as a window, then quickly looses its titlebar, and
appears to be a sheet again. However, I can easily
drag the main app's window around while the sheet
stays put. Clearly, that's not what I'd like.
Any ideas on why it's different one way, even though
the underlying code is the same? I've stepped through
it and the value for modalForWindow is non-nil either
way, so I get the sense it's more subtle than that. :|
All ideas and suggestions would be appreciated.
Thanks!
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden