289
Macro File Editing Rules
A
ppen
dix
does not operate in router mode, these settings are not
used.
O: SET AVAILABLE SOURCE/DESTINATION
Set the source and destination ranges so that the MVS-
3000 inputs and outputs can be selected.
R: SET ROUTE
Since when using the simple connection the switcher and
router cannot be connected in cascade, no route setting is
required, and this is unset.
Y: SET DISPLAY MODES
The DISPLAY MODES/PANEL FUNCTION setting is
set to NORMAL.
The TALLY GROUP setting is set to be the same as the
setting in Engineering Setup >Router/Tally >Group Tally
menu (7362) on the MVS-3000.
Z: SET PANEL STATUS
The various settings are the same as the factory default
settings.
Macro File Editing Rules
When editing a macro file, follow the rules described
below.
Macro File Syntax
The macro file syntax is as follows.
File format
The file is in CSV (comma-separated value) format.
Newline code
CR (ASCII code 0D), LF (ASCII code 0A), or CRLF may
be used.
Statement syntax
There are four types of statement, each terminated by a
newline code.
File header:
This must always appear as the first line of
the file. It comprises 28 characters, as follows.
Example: PNL (space) 0001PNL_rrrr.PMRnnnnnnnn
rrrr: Macro register number (0001 to 0099)
nnnnnnnn: In a file created on the switcher, this is a
register name automatically set by the switcher.
When creating a new file, it is recommended to set this
to be the same as the file name
.
The name is limited to eight characters.
The following characters may not be used.
space, \, /, :, ;, , (comma), . (dot), <, >, *, ?, ", |
Comment:
Begins with “#”. The content of the line
following the “#” up to the next newline has no effect
on macro execution, and can be used as a comment.
You can only use comments in files saved to a local
disk or removable disk. When you load a macro file
into a register, the comments are discarded.
Event statement:
Begins with “Event?”, and defines the
macro event. For details, see
Continue statement:
Begins with “Continue?”, and
defines the macro event.
For details, see
Some events cannot be used
between Events and Symbols” (p. 290))
.
Syntax of Event and Continue
Statements
An event can be written with an Event statement only, or
with an Event statement followed by any number of
Continue statements. The Event statements and Continue
statements have the following syntax.
Word separator character
Use “,” (comma).
Ignored
Spaces and tabs are ignored. There is no distinction
between lowercase and uppercase. If two or more
separator characters appear consecutively, later ones are
ignored. Separator characters at the beginning of a line are
also ignored.
Content of line
Must begin with “Event?” or “Continue?”, followed by
symbols and parameters.
Event?,[symbol], [parameter], [parameter], …
Continue?,[symbol], [parameter], [parameter], …
symbol:
ASCII character string showing the type of event
“Correspondence between Events and Symbols”
.
parameter:
Shows details of an event. Consists of
parameter names and arguments, and these must
appear in pairs. The number and type of parameters
depends on the event
.
If the same parameter appears twice or more, the last
occurrence is valid.
Notes
