A
Alain O'Dea
Currently undo in Visio covers actions like switching pages and each step
taken in moving an object. I recommend that actions like switching pages and
the intermediate steps of a move be left out of the undo stack . I recommend
that only the start and end points for moves of a single object or group of
objects be stored in the undo stack. This would make undo/redo appear to be
much faster and allow for a perceptually deeper undo stack.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...a047c4731d7&dg=microsoft.public.visio.general
taken in moving an object. I recommend that actions like switching pages and
the intermediate steps of a move be left out of the undo stack . I recommend
that only the start and end points for moves of a single object or group of
objects be stored in the undo stack. This would make undo/redo appear to be
much faster and allow for a perceptually deeper undo stack.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...a047c4731d7&dg=microsoft.public.visio.general