Ah, ok, this is more like what i wanted to hear! :) I understand how
@dynamic works, but how to I get to funnel all calls to @dynamic
properties to the same call such as setValue:forKey: or something like
that where i can parse the key and update my internal data and set the
flags i need to set.
thx
AC
On Sep 3, 2009, at 2:43 PM, Jens Alfke wrote:
On Sep 3, 2009, at 11:32 AM, Alexander Cohen wrote:
Ok, thats what i thought. But just for implementation ideas, how
does CoreData know when one of it's @dynamic properties is changed?
It must set some sort of flag somewhere in order to know what to
write out when it needs to save. How does it handle that?
@dynamic properties are assigned implementations on the fly at
runtime. NSManagedObject's implementation of the setter method
includes setting the dirty flag, I suppose.
So actually my "no" wasn't strictly true. You can track changes to
arbitrary dynamic properties, including those defined in subclasses,
because they all funnel through a common implementation.
—Jens_______________________________________________
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/alexcohen%40toomuchspace.com
This email sent to [email protected]
_______________________________________________
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]
