Download D3PLOT 12.0 user manual

Transcript
D3PLOT
User manual Version 12.0, October 2014
8.3.2 Previewing commands.
The playback control panel can be operated in Preview (instead of
Playback) mode. This allows you to view commands without actually
executing them, and thus to position yourself where you want in the file.
The PLAY > button is replaced by a PREVIEW > one to remind you which mode you are in. Commands are listed in
the Current command status box as above, and you can STEP backwards and forwards as before. These and the
other positioning and searching commands operate in exactly the same way as for recording session files: see Section
8.2.2 for more detailed instructions.
8.3.3 Handling errors during playback.
When you are playing commands it is possible to generate errors. Examples might be playing back commands
recorded in a model with 10 materials in a different one with only five materials. If the screen button corresponding to
the (non-existent) 10th material is picked in some context (eg from a menu) an error will occur.
The ERRORS... command lets you set the action to
be taken when errors occur.
The Action on errors options are shown here, with
the default Warn and continue option set.
The other options are self-explanatory.
Section 8.5 gives more information about how errors
may occur, and how to avoid them.
8.3.4 Opening new command files.
You can read in a new command file at any time, or reread the current one (assuming it has been updated on disk).
In either case all existing commands in the internal scratch file are deleted and superseded by those read in. You
cannot concatenate the contents of the new file with the existing one.
8.3.5 Recording session files during command file playback.
This is quite legal. The two operations are quite separate, and commands executed from a command file will be
recorded exactly as if they had been typed in. This is the recommended method of editing and appending to session
files.
8.4 Using the “launcher” box
during recording and
playback
This figure shows the command/session file "launcher"
box part of the way through a simultaneous record and
playback session.
This box need not be mapped, but it can be useful to use it
rather than the full control panels since it uses less space.
The "launcher" box always echos the
PLAYBACK/STOP status of the playback box if a
command file is resident in memory.
Page 8.6