Change the Load Order of NIB Objects?

[mekronk]

Hi All,
I’ve got some classes that I’ve instantiated (is that a word?) in interface builder. Object A loads preferences from user defaults into its properties in its init handler. The other nib objects use these properties when they are instantiated when the application first runs. There is a problem however if Object A doesn’t load first. Is there a way to specify that object A should instantiate before the other object in interface builder? Thanks.

[fiz]

Hi Mekronk,

From the docs:

NSNibAwaking Protocol Reference

(informal protocol)

Framework
/System/Library/Frameworks/AppKit.framework
Companion guide
Resource Programming Guide
Declared in
NSNibLoading.h

Important Because the order in which objects are instantiated from an archive is not guaranteed, your initialization methods should not send messages to other objects in the hierarchy. Messages to other objects can be sent safely from within awakeFromNib”by which time it’s assured that all the objects are unarchived and initialized (though not necessarily awakened, of course).

Sorry for the bad news.

Regards,

[mekronk]

OK. I suspected that was the case. When testing, it the instantiation seemed random. I just couldn’t find it in the documents anywhere. Many thanks for digging that up for me.