This clearly was my fault. In the NIB loading of NSIBObjectData the old code was looping over the _names map to instantiate the objects. I changed that to the _objects map which looked better to me. As your results show this isn't true I changed that code back again. That way the owner once more gets awakened :-)
Sorry for breaking this, Fred Am 25.03.2010 19:33, schrieb Doug Simons: > Unfortunately, this only gets us to the next problem: awakeFromNib is > not being called on the nib file's owner. > > In digging through this issue in gdb I noticed that this nib is > another one that contains objects which load other nib files in their > init methods. I don't think this is the cause, because I think we > have other nibs that do the same that are loading okay, but I thought > I'd mention it. > > I didn't see where the code is supposed to call awakeFromNib on the > owner -- is the file's owner supposed to be one of the regular > objects in the nib's list of objects? It's not in that list. > > Also, I noticed that one of the objects that is in the list is a > custom object that resolves to NSApp, causing awakeFromNib to be > called on NSApp for EVERY NIB that is loaded. This seems wrong to me > (although it isn't causing us any trouble). In fact, I just set a > breakpoint on our application's awakeFromNib on Mac OS X and verified > that it is only called once by Cocoa, when the MainMenu nib is > loaded. > > Doug _______________________________________________ Gnustep-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnustep-dev
