Re: connections and the nib lifecycle
Re: connections and the nib lifecycle
- Subject: Re: connections and the nib lifecycle
- From: Chris Hanson <email@hidden>
- Date: Wed, 21 May 2008 20:27:19 -0700
On May 21, 2008, at 11:00 AM, Vijay Malhan wrote:
But the problem is still open for discussion. Is there any
differences in sequence of events occurring while loading of Nib
between Tiger and Leopard platforms?
There really should not be, at least not like this. As I explained in
my response to Torsten, just instantiating an NSWindowController does
not cause it to load its nib; invoking -[NSWindowController window]
causes that to happen as a side-effect.
So just doing [[MyWindowController alloc] init] does not load
anything. Only asking for its window will cause a window controller
to load a nib file, and when it does so, the window controller will
get a sequence of messages like this:
You send this:
-window
The window controller sends itself these:
-windowWillLoad
-loadWindow
-awakeFromNib
-windowDidLoad
There's nothing particularly magic here. I just suspect that in some
cases, people have an "extra" window controller object in their nib
file, in addition to the window controller that loads the nib file and
acts as its owner (File's Owner).
-- Chris
_______________________________________________
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