Undo-Redo

Undo and redo actions performed in HyperWorks.

Not all the actions performed in HyperWorks can be undone or redone. If an operation does not support undo/redo, the undo/redo functionality will be disabled once the action is completed and any previous undo/redo history recorded will be reset. The undo/redo history will also be reset every time a macro or other tcl application is invoked.
Note: The undo/redo functionality is supported by most HyperWorks panels, tools and user interface functionalities.

By default, the number of undo actions is set to 100 and the maximum undo memory (MB) is set to 2500. You can modify both of these settings by going to File > Preferences > Performance.

Undo/redo history may use a large amount of memory. By default, a threshold of 80% of the total memory limit will not be exceeded. Once the memory threshold is exceeded, all older actions will be automatically purged.

  • Undo an action by clicking Edit > Undo from the menu bar, or pressing Ctrl+Z.
  • Redo an action by clicking Edit > Redo from the menu bar, or pressing Ctrl+Y.
Tip: Simultaneous actions can be undone/redone by selecting them from the Undo/Redo menus on the menu bar.


Figure 1.

HyperView Supported Actions and Known Limitations

Supported Actions

Undo-redo is implemented primarily to support actions related to changing the visibility or other attributes of the following entities:
  • Components, Systems, Assemblies, Includes, Parts, Model files, Materials and Properties.
It is meant as a powerful alternative to the Restore and Reject buttons in the Entity Attributes panel and it is strongly recommended to use this feature and the browser for such operations instead of the panel.
Note: The supported action itself could be performed via the browser or through any of the panels or toolbars that control visibility and entity style (for example: Entity Attributes panel, Mask panel, Visibility Controls toolbar) and it will get recorded in the undo-redo stack in the browser.

Known Limitations

  • Not all actions can be undone or redone.
    • For example, creation and deletion of any entities such as notes is not recorded at this time. This will be addressed in a future release.
  • Undo/Redo of Apply style operation does not dynamically update the visibility and FE style of the components in the browser.
  • There are a few cases where an action could get recorded as more than one operation in the undo stack. In such cases, you might have to click on undo/redo several times to completely reverse the action.