After sleeping on this issue a little, I've made some progress. The errant -updateChangeCount: occurs when an attribute of the object in question, which is nil to begin with, is re-set to nil. This setting happens when a detail view gets bound (Cocoa Bindings). I'm still digging into why that happens (54% of the time); it's complicated but it's a different issue.
I find it annoying that -updateChangeCount: would be invoked when an object's attribute experiences such a non-change, but I seem to recall that, in general, Cocoa does not check to see if changes are really changes. In the past, I've put in my own filters for this, to improve performance, for example. Jerry _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
