Am Do,14.08.2008 um 07:46 schrieb Jeff Hellman:
Hi Folks-
Hi
as already said, KVO is not the right place to do that.
If this is a real important property, you should think about a model
user interface (update button, sheet) to handle it. You can use
notifications or maybe "bindings through through a controller".
But first you have to think aboout the semantics of an undo. Is this a
new change or should the update value go back to the last change
before the undone opertation? Maybe a "real" change history would help
yoou.
Cheers,
Amin
I've got a document based CoreData application.
When I open a file and add some of my NSManagedObject subclass objects
to either an NSArrayController (bound to an entity in my NIB) or
NSObjectController (-setContent) the
- (void)willChangeValueForKey:(NSString *)key
is called. So is
- (void)didChangeValueForKey:(NSString *)key
Why is this? I'm not actually changing the object values, am I?
Thanks-
Jeff
--
Jeff Hellman
[EMAIL PROTECTED]
_______________________________________________
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/negm-awad%40cocoading.de
This email sent to [EMAIL PROTECTED]
Amin Negm-Awad
[EMAIL PROTECTED]
_______________________________________________
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 [EMAIL PROTECTED]
