This shows you the differences between two versions of the page.
rhino:futurehistory [2015/09/17] |
rhino:futurehistory [2020/08/14] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Future History====== | ||
+ | |||
+ | >Using Rhino' | ||
+ | |||
+ | =====The undo stack===== | ||
+ | |||
+ | Rhino was one of the first CAD programs to have virtually unlimited undos. | ||
+ | |||
+ | Rhino’s //undo stack// (list of commands that are available to undo) lets you try out a lot of things without fear and see if you like them. You can always go back if you don’t. | ||
+ | |||
+ | Undo needs memory, of course. | ||
+ | |||
+ | =====Future History, or a blast from the past===== | ||
+ | |||
+ | Rhino' | ||
+ | |||
+ | Or, you get to a stage where you realize you need something many operations ago, but you deleted it. You don’t want to have to redo all your later operations, but you need that deleted object. | ||
+ | |||
+ | =====Undo or redo many steps at once===== | ||
+ | |||
+ | A couple of commands that are useful are **UndoMultiple** and its companion **RedoMultiple**. | ||
+ | |||
+ | **Note:** Once you have undone several commands, if you want to go forward again, //**do not execute a new command!**// | ||
+ | |||
+ | If you decide you want to have a new file with a copy of the model at a previous state in the session, you can back up to the point you want – but – do not use the command **Export** or **SaveAs**. | ||
+ | |||
+ | A limitation on this technique may be the memory capacity of the Windows clipboard, as well as the RAM of your machine. | ||
+ | |||
+ | =====Undo for selected objects===== | ||
+ | |||
+ | **UndoSelected** lets you undo operations performed on a particular object without undoing later operations. For example: Make a box, move the box, move the box again, fillet the edges of the box. Make a circle, make a rectangle. Select the box and start **UndoSelected**. If the operations on the box are still in the undo stack, you get a list of operations to undo. You can undo these without affecting the circle and the rectangle that were made after these operations. Note that the entire operation is undone. If other objects were moved with the box, they will also be //unmoved// by **UndoSelected** on the box. | ||
+ | |||
+ | |||
+ | =====Incremental save===== | ||
+ | |||
+ | Of course, this sort of //history// only applies to the working session. Once you have closed the file, the undo is erased. So your history is definitely lost at that point. | ||
+ | |||
+ | One way to have previous versions go back to between sessions on a particular file is to use **IncrementalSave**. | ||
+ | |||
+ | |||
+ | |||
+ | |||