On Nov 13, 2010, at 15:20, Charlie Dickman wrote: > Notably, I executed using GDB and watched it get to the method and fail to > assign values.
FWIW, there are perhaps 3 "ordinary" causes of this sort of thing: 1. You try to do this at a point in time when the outlets haven't been established yet. This is the one Andy talked about. Although you already moved the code to 'awakeFromNib', it's worth trying to check *later* in your application's execution to see if the outlets are set eventually. If not, this probably wasn't your problem. 2. You didn't really hook up the outlets in IB. Only you can check that, and you have, but it's worth keeping in mind that it's easy to talk yourself into believing that you've done it right when you haven't. (Speaking from painful personal experience here.) 3. You actually have 2 instances of the class, and you're seeing the misbehaving code executing in the wrong one -- the one that didn't get its outlets established -- while the one that had the correct outlets has been leaked or deallocated. _______________________________________________ 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
