On 2009 Nov 13, at 19:50, Kyle Sluder wrote:
On Fri, Nov 13, 2009 at 7:44 PM, Jerry Krinock <[email protected]> wrote:
Maybe you or someone could explain it a little better?
See Graham's explanation.
Got it. "Known bug."
Yes it does, but once you build a Core Data app which is more
complicated
than DepartmentAndEmployees, you'll be very disappointed with out-
of-box
Undo operation. One problem is that users typically need to click
Undo
several times to undo what they may have done with one click.
There are
threads on this in the list archives, or google: core data undo
fishmeal.
That doesn't change the fact that, by default, you already have an
undo group opened for you. Unless you're suggesting that you disable
this behavior?
Well, actually I did try to -setGroupsByEvent:NO once, but quickly
concluded that this idea is a non-starter when Core Data is in the
house. What I do is to wrap the several undo groups that Core Data
creates into one nested undo group. I end the undo grouping in a
performSelector:withObject:afterDelay:. It works pretty good most of
the time.
Thanks, Kyle.
_______________________________________________
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]
