I have a rather complicated undo setting
I encountered a similar situation where I had multiple plugins each
with their own NSManagedObjectContext and thus their own undo manager.
I solved it by implementing an NSProxy subclass which held references
to all the undo managers and was
Hello,
I have a rather complicated undo setting
My document Object has a Array of independent graphical items
(containing some properties).
Each item should have its own undo/redo based of selection in the
interface. So I select Item_1, modify it, select Item_2 and modify it,
too. Then I
On Jul 5, 2008, at 04:07, Georg Seifert wrote:
My document Object has a Array of independent graphical items
(containing some properties).
Each item should have its own undo/redo based of selection in the
interface. So I select Item_1, modify it, select Item_2 and modify
it, too. Then I
My document Object has a Array of independent graphical items
(containing some properties).
Each item should have its own undo/redo based of selection in the
interface. So I select Item_1, modify it, select Item_2 and modify
it, too. Then I want to be able to select item_1 again and undo
On Jul 5, 2008, at 11:37, Georg Seifert wrote:
But than I have just another question: If I select more than one
object. All the handling of the undos of the single object I can do
in the undo/redo functions of my delegate. But how do I tell the
menu that the is something to undo? I would
I've done a lot of stuff recently with Undo in my DrawKit project,
which sounds a little like what you are doing also. I have to say,
having one undo manager per object sounds like a recipe for confusion.
It's just not how undo is intended to work, and not how users expect
Undo to work.
