undo

The user can undo "backwards", the default, or undo "forward" (an undo backward must precede an undo forward). In other words, the user can move backward and forward in the operation stack. Adams View lets you set the number of operations to be "remembered", for use by the UNDO command at later time. You set the number of operations with the command: UNDO SET STEPS_STORED=. The default number of steps stored is five.

The UNDO command works only on the last operation performed by the user. For example, if you wanted to undo an operation that occurred five commands previously, you would have to undo the last five commands, starting with the most recent. You cannot selectively choose which command remembered by Adams View will be undone.

The UNDO supports grouping of Adams View commands into blocks. Once defined, these blocks may be undone with a single UNDO command. An UNDO block is defined by issuing the command UNDO BEGIN_BLOCK to mark the beginning of the block. All following Adams View commands will be included in the UNDO block until the block is closed. The UNDO block is closed by issuing the command UNDO END_BLOCK.

You may define your own UNDO BLOCKS around macros, command files, or any group of Adams View commands. This allows the sum of operations performed in the command file or macro to be reversed by a single selection of the UNDO button.Once the UNDO block has been closed individual commands and nested UNDO blocks within the UNDO block may not be effected. Once closed, the UNDO block may not be opened again.

The limitation on the number of commands remembered by the UNDO SET STEPS_STORED does not apply to commands nested within an UNDO block. Care should be taken not to allow too many commands to collect within an UNDO block. You may experience unexceptable system performance if too many commands are stored in a single UNDO block.

The ‘write_to_terminal’ parameter is most likely be used in conjunction with the FILE_NAME parameter to get the information put to a file only.