Using [undo, Command history – ETC Eos Titanium, Eos, and Gio v2.0.0 User Manual

Page 278

Advertising
background image

260

Eos Titanium, Eos, and Gio Operations Manual

Using [Undo]

Undo is a method to reverse or “undo” certain operations performed in the software.You can use
[Undo] to reverse any command that results in a change to data that would be saved to the show
file or any command that changes manual levels in live.

If there are any commands in the command line, pressing [Undo] once clears the command line.
Once the command line is empty, pressing [Undo] will start the undo process.

When [Undo] is pressed from an empty command line, the command history display will open in
the CIA and the most recent completed command is highlighted in gold. If you press [Enter], you
will undo your last command. [Shift] + [Clear] can be used to clear the command line as well.

You may use the page arrow keys or the touchscreen to select multiple commands. When [Enter]
is pressed, an advisory is posted. When [Undo] is pressed again, all highlighted commands will be
undone and subsequently removed from the command history. When removing more than one
command, a confirmation is required.

After an Undo has been performed, a {Redo} button will appear in the command history. You may
press this button followed by [Enter] and the last undo will be “redone” to reinstate the removed
commands

In a multiple user environment, each user is only able to undo the changes that they made. In the
undo command history, the user will only see the commands that they used.

Command History

Command histories are kept for each editing session, which begins when:

• a desk logs on to the network

• a new show file is loaded

• a show file is opened, merged, or imported

Each user builds an individual command history, specific to the commands they have entered.

You can open the command history at any time by pressing <More Sk> {Cmd History}.

Commands that do not affect manual input or record targets (loading a cue, running a cue, or
moving a submaster) are not included in the command history.

N o t e :

Not all commands can be undone including playback actions and manual

attributes placed on channels or encoder actions.

Commands to be

undone

Advertising