On Fri, 5 Feb 2010 13:04:06 -0800 (PST), Keith Blount <keithblo...@yahoo.com> said:
>in its nib somewhere internally, but it *is* getting released after all. The problem is that during 3), the project that is loading sends out some notifications while the array controller is still around, so the array controller still in memory picks them up and checks to see if they are coming from its main document or window controller, but these no longer exist so it panics and quits. It's funny you should mention this, because I was just groaning the other day about how difficult it is to debug notifications. Where notifications are under my control (i.e. I am the one who is posting them and/or registering to receive them), I have recently adopted a policy of registering in as specific a way as possible, as late as possible, and of unregistering specifically and as soon as possible. But even so there can be problems, and the fact that it is *still* after all these years of Cocoa impossible to ask an NSNotificationCenter to display its dispatch table, for debugging purposes, is simply inhuman. I've had a bug in on this for years, which remains open. m. -- matt neuburg, phd = m...@tidbits.com, <http://www.tidbits.com/matt/> A fool + a tool + an autorelease pool = cool! AppleScript: the Definitive Guide - Second Edition! http://www.tidbits.com/matt/default.html#applescriptthings _______________________________________________ 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
