Op 12 nov 2010, om 20:44 heeft Quincey Morris het volgende geschreven:
In case 2, which seems like the superior solution, the private dictionary isn't being accessed via KVC at all, so the only KVC behavior you're concerned with is that of the wrapper.
Ah, that explains. If I understand it correctly, for all properties, each and everytime, valueForUndefinedKey is called? So I do also need to override setValue:forUndefinedKey in case 2? To make sure that the properties end up in the dictionary? Basically it's the same to what I've now (based on the discussion with Graham), but adding "Undefined" to my method names, I do keep the performance enhancements of the original implementation?
Kind regards, Remco Poelstra _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
