Re: (no subject)
Re: (no subject)
- Subject: Re: (no subject)
- From: Jeff LaMarche <email@hidden>
- Date: Thu, 6 Jun 2002 13:16:04 -0700 (PDT)
On Thursday, June 06, 2002, at 06:43PM, Tommy Knowlton <email@hidden> wrote:
>
I've got a NSWindowController subclass instance in my application's main
>
nib.
>
It's _window outlet is connected to the only NSWindow in the nib.
>
I need to do some processing at a time BEFORE the window is shown on
>
screen, but AFTER all outlets have been connected for all nib objects.
>
-(void)awakeFromNib does not get called reliably such that all outlets
>
on all nib objects have been connected.
>
Unfortunately, experience seems to be teaching me that
>
-(void)windowDidLoad does not get called for NSWindowController's that
>
are instantiated in the nib.
If you're finding that awakeFromNib is not getting called reliably, you should log it as a bug. I've never had issues with this, and Apple's documentation states:
"If you need to initialize an object after its nib file has been loaded, create an awakeFromNib method for the object. It's called after all nib file's objects have been loaded and all the connections have been set up."
so, it sounds like awakeFromNib is what you want, but that there's an issue either with Apple's framework or the structure of your nib.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.