On Feb 16, 2013, at 6:50 PM, Jerry Krinock <[email protected]> wrote: > > On 2013 Feb 16, at 18:24, Kyle Sluder <[email protected]> wrote: > >> ;Any reason you didn't do this in the nib itself? > > Probably because I generally find it more enjoyable to write code rather than > click and poke my way through Interface Builder.
Well, at least delegates are pretty straightforward. But that shouldn't have had anything to do with it, and I'm glad it didn't. > >> I'm wondering if you're hitting that caveat from the resource Programming >> Guide where AppKit cannot guarantee that -awakeFromNib is sent to File's >> Owner last, and there's some ordering issue with respect to -setDelegate: >> and the drawer receiving -awakeFromNib for which IB has a hack to work >> around. > > OK, upon re-reading the warning in -awakeFromNib documentation I see what you > mean, if the drawer is considered to be "in the hierarchy". The hierarchy consists of all objects in the nib. Since there can be multiple top level objects, it's really a forest, not a tree. > > So I changed my project to wire up the delegate in the nib instead of > -awakeFromNib. > > Quick Result: > > First launch: It worked. > Second launched: It failed. > > I'm going to do some more debugging while it's in this state. Huh, here's another W.A.G.: perhaps it has something to do with NSWindowRestoration? --Kyle Sluder _______________________________________________ Cocoa-dev mailing list ([email protected]) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
