[NSObject setValue:forUndefinedKey:] no longer requires explicit KVC notifications?
[NSObject setValue:forUndefinedKey:] no longer requires explicit KVC notifications?
- Subject: [NSObject setValue:forUndefinedKey:] no longer requires explicit KVC notifications?
- From: Gabriele de Simone <email@hidden>
- Date: Fri, 7 Aug 2009 14:50:53 -0400
It used to be that if you overrode -[NSObject
setValue:forUndefinedKey:] your own subclass was responsible for
calling -[NSObject will/didChangeValueForKey: so that bindings and
observers would work as expected.
That was fine, since it allowed one to provide different
implementations depending on the key, and to generate (or not) KVC
notifications. It seems that a recent update to Mac OS X (perhaps
10.5.8?) has changed this behavior. It seems that as long as you
override setValue:forUndefinedKey:, KVC-compliant notifications are
automatically generated for the given key.
Can anyone confirm this? This is an "interesting" change to the Cocoa
framework that probably interferes with any class that overrides
[NSObject setValue:forUndefinedKey:].
Thanks,
Gabe
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden