Message Boards Message Boards

18
|
17877 Views
|
10 Replies
|
45 Total Likes
View groups...
Share
Share this post:

So I added this small feature to v10 called multiple undo

POSTED BY: John Fultz
10 Replies

Hello I missed this original post. Here is a belated congratulations to John and team on this spectacular achiement! WCC

POSTED BY: W. Craig Carter
Posted 10 years ago

Nice work. I checked that in situ image modifications via the toolbar that appears when an image is clicked are undoable. The undo makes the workings of the "Actions & Tools" menu clumsy. I would prefer to remove the mini-preview of a modification and show the whole image and let "Apply" be the default. The equivalent of "Cancel" is just a ^Z away. (Not to mention possible multiple undo's).

POSTED BY: Douglas Kubler
Posted 10 years ago
POSTED BY: Andrew Meit
Posted 10 years ago

You single-handedly have convinced me to upgrade. I hope you get the big raise this year.

POSTED BY: Eric Meyers

Thank you John. And, I am sure, a loud thank you from the silent majority as well.

However, the Redo documentation seems to need editing as it talks about Undo rather than Redo and seems to say that one can only do a single level of Redo/Undo. (But Redo does work!... it's just a documentation issue.)

http://reference.wolfram.com/language/ref/menuitem/Redo.html

POSTED BY: David Reiss

Multiple undo has been number 1 on my wish list for years. Naturally, now that it's been done, I tell what number 2 is: the ability to split the notebook view and look at two different parts at the same time. That's so I can look at functions I've defined at the top of the notebook when I go to use them at the bottom.

POSTED BY: Frank Kampas
POSTED BY: Michael Croucher

Yes, there is some of the information you can get to programmatically (and even triggered using Dynamic). But it's undocumented and should not be considered an interface that will be stable through future versions.

CurrentValue[FEPrivate`UndoInformation[_NotebookObject, _Integer:1]]

Every notebook has its own undo manager, so the NotebookObject reports undo information for that notebook only. Input fields also have their own undo manager, if you wanted to see the undo information for an InputFieldBox, you could pass in a BoxObject instead.

The integer is just an indication of how many levels of the stack you want returned. The default is 1 (just the most recent thing). If you want everything, just pass a big machine integer, like 999999.

Also, you can use RedoInformation to get information about the redo stack instead.

Example:

CurrentValue[FEPrivate`UndoInformation[EvaluationNotebook[], 999999]]
POSTED BY: John Fultz

John, I just wanted to let you know how much I appreciate your efforts. Not only that you implemented multiple undo for version 10, but the general attitude to listen what the users have to say and to explain why some features don't work or cannot be implemented easily. I'm always amazed that you still show up in the stackexchange chat every now and then, although everyone will instantly fire questions at you. I do know that a company like Wolfram always sits in many chairs when it comes to feature/design decisions and that Wolfram needs to make profit, because after all the employees like you need to be paid. This makes it even more precious that so many of you guys try to connect to the user base.

Thank you and all the people having "Comments & opinions expressed here are mine, and not those of my employer" in their SE profile for that.

Patrick

POSTED BY: Patrick Scheibe

Congratulations John! It's an amazing advance to user experience.

For me, this was the biggest complaint from new users. And now has just gone.

POSTED BY: Rodrigo Murta
Reply to this discussion
Community posts can be styled and formatted using the Markdown syntax.
Reply Preview
Attachments
Remove
or Discard

Group Abstract Group Abstract