> In general, it's not necessary for the observer to keep a copy of the old > array. However, there's a longstanding bug in NSArrayController that means it > doesn't pass the correct change information, so the sample code you're > looking at might be working around this bug. It's only lame because there's a > lame bug.
Sounds like a good news, assuming that NSTreeController does not have this bug, right? It is still unclear though how do I observe NSTreeContoller, or NSArrayContoller if it didn't have its bug. Can you give me an little example? I made an experiment myself and found that when I add a node to the tree, I receive the NSKeyValueChangeSetting change, and no old/new values (NSNulls) in the change dictionary, although I specified it in the options of addObserver: message. I wonder if this is by design and what I am supposed to do? How do I find out the change? _______________________________________________ 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 [EMAIL PROTECTED]
