Matt, you have written a good essay illustrating the many twists, turns and corners you get into when trying to track Undo yourself. Redo adds even more complexity.
On 2014 Jan 29, at 07:30, Matthew LeRoy <mle...@minitab.com> wrote: > Am I on the right track, or is there some other recommended pattern here? My recommended pattern is to use Core Data in any app that requires Undo to really work. Boom - Undo is done, and Apple has covered the edges and corners much better than I'd ever have time to. Admittedly, using Core Data introduces other issues, but, unlike home-made Undo, these issues are finite and manageable. On 2014 Jan 29, at 08:07, Keary Suska <cocoa-...@esoteritech.com> wrote: > In my experience, manipulating NSUndoManager's stack is an exercise in > frustration, as NSUndoManager's gets itself into an inconsistent state. IMHO > this is largely due to the opacity of the class, and the near complete lack > of introspection available. Use an Undo Manager which is not opaque… http://apptree.net/gcundomanager.htm _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
