Re: awakeFromNib vs appdidfinishlaunching
Re: awakeFromNib vs appdidfinishlaunching
- Subject: Re: awakeFromNib vs appdidfinishlaunching
- From: Karim Morsy <email@hidden>
- Date: Wed, 22 Mar 2006 16:23:31 +0100
thanks for the info!
then the app did finish notification gets sent after all obejcts have
been sent awakeFromNib, right ?
in order for the app to launch faster it would be better to have cpu
intensive initialization in appdidfinischlaunching handler ?
thanks,
Karim
On Mar 22, 2006, at 3:32 PM, Jack Nutting wrote:
On 3/22/06, Karim Morsy <email@hidden> wrote:
it's said that upon instantiation all objects are sent awakeFromNib
(in an arbitrary order).
but are all obecjs instantiated first and then each one is sent
awakeFromNib OR is an object instantiated, sent awakeFromNib, and
then the next object is instantiated, sent awakeFromNib and so
on ... ?
in the latter case, this would imply that all initialization of
objects done in the controller (for example setting values for
sliders, textFields, drawing custom views etc) should not be done in
awakeFromNib as some of them might not yet be existing, right ?
Whenever a nib is loaded, all object within the nib are
initialized, and THEN all objects are sent awakeFromNib. So
whenever awakeFromNib is called, you should be able to rely on all
other objects in the nib having been initialized.
--
// jack
// http://www.nuthole.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