[object setValue:@"1" forKey:@"attr"];
[self forceUndoBoundaryInContext:context];
[object setValue:@"2" forKey:@"attr"];
This is a little odd. If this is in the UI thread, it will be
confusing to the user in the typical scenarios. Are you sure you
don't want to create a nested undo group ?
This is actually pretty far removed from the UI. I'm managing internal
state that I want to be able to roll back to specific points. A single
rollback group may span many events. Imagine a stack of mutable
dictionaries, each one of which starts out as a copy of the one
before. Except with a managed object model, I can have complex,
documented structures and I don't have to worry about making deep
copies of nested mutable objects.
Fiddling with the undo groupings themselves should be done with
NSUndoManager API.
That's what I ended up doing, so I guess I was on the right track.
Thanks for the quick reply,
Peter
_______________________________________________
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]
