Well, that was easy to test and indeed I found that you found a bug in my idea. The only way to fix it would be if we Apple had given us a - didUnturnIntoFault method, but they did not.So, it looks like, for observing changes to the properties of managed objects --- * Using NSManagedObjectContextObjectsDidChangeNotification is no good since it doesn't give you specific information on the current change which actually caused the notification. * Using KVO is no good because observers must be removed before an object becomes a fault, and there is no mechanism to find out when the object un-becomes a fault, which you need to restore your observers.
bug numbers ? 'cause if it's not important enough for you to even file an ER, it's unlikely to be as important as the bazillion other things we have to do, as far as the eye can see...
- Ben _______________________________________________ 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
