On Dec 6, 2009, at 10:20 AM, Mike Abdullah wrote: > On 6 Dec 2009, at 13:30, Andy Lee wrote: > >> On Dec 6, 2009, at 7:36 AM, Graham Cox wrote: >>> My fourth approach is to write my own bloody undo manager and have done >>> with it. Result so far - bliss. >> >> FWIW, Wil Shipley agrees about the bliss part: >> >> <http://wilshipley.com/blog/2007/12/transitions-and-epiphanies.html> >> >>> I was so into using CoreData's magic undo that I kept going farther and >>> farther to make it work, when I really needed to say, "Ok, this doesn't >>> work in this situation, I'm doing my own undo in 40 lines of code." >> >> I haven't worked with NSUndoManager myself, but my takeaway from this (and >> also from a friend who was also frustrated with it) is that it's great for >> very basic scenarios, but if I ever find myself getting frustrated with it I >> shouldn't hesitate to write my own. > > Er, Wil's post has nothing to do with Graham's problem. Wil ran into issues > fighting Core Data's built-in undo registration and decided the best approach > to manually record undo information himself instead. I am almost 100% certain > Wil didn't then proceed to chuck out NSUndoManager. He just turned off Core > Data's use of it.
True, the contexts are different. My point was that if built-in undo doesn't work for you for whatever reason, it's not wacky to consider writing your own. Usually when one starts down this road it's reasonable to wonder whether you're missing something and fighting the frameworks. --Andy _______________________________________________ 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 arch...@mail-archive.com
