Re: Nib files and outlets

FROM : Björn Carlström
DATE : Sun Nov 28 16:53:30 2004

I could load it in advance but the window is rarely used, so I put it 
in a separate nib to save some memory.

Here's what I'm trying to do.
I have a controller  (A) that creates a windowController(B) and loads 
the window and a controller(C) that manages a tableView in the window. 
I want to access controller (C) to set up the information in the 
tableView, but the outlet in the windowController(B) point to nil. The 
next time I access the windowController(B) its outlet correctly points 
to controller(C).

How do I set this up with awakeFromNib:? None of the objects in the the 
nib file has any reference to controller (A). Do I need to set a 
reference in the windowController(B) to controller (A) when its first 
loaded, so that awakeFromNib: can call controller (A) and ask it to do 
the appropriate setting up?

All this seems a little bit akward. Perhaps its better to load it in 
advance use some extra memory and stay away from the problems?

Björn

2004-11-28 kl. 11.38 skrev Jiri Volejnik:

>> Using awakeFromNib would give the user the opportunity to trigger 
>> something else

> I don't think so. It's not done in parallel. However, you can load 
> your nib in advance, and just show the window when user clicks the 
> button.
> Jirka
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list      (<email_removed>)
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/cocoa-dev/
> <email_removed>
>
> This email sent to <email_removed>
>