On Jan 27, 2011, at 16:43, Bruce Cresanta wrote: > I have and NSDocument based application with the standard MyDocument > document. I have a view declared as an IBOutlet in the document and use IB > to hook up the view variable to the contentView of the window that gets > created. When I put a log message in awakeFromNib, it gets called twice > with identical execution traces. The first time awakeFromNib is called, > all the IB connections resolve. The second time it is called, none of the > IB connections resolve and are nil. Would you please help me think > through what's going on?
The most usual cause of this kind of thing is accidentally creating 2 NSDocument objects. For example, when trying to hook up outlets in IB, some developers end up putting a NSDocument object *inside* the NIB. That causes a second document object to be instantiated. (The other is created programmatically by NSDocumentController when you open or create a document.) Use the debugger to look at the value of 'self' each time you get to 'awakeFromNib'. I bet it's a different value. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
