| TEXT |
The Option File is tree-structured so if you think of a tree with a
Primary Menu as its trunk, as you move up the branches the ENTRY ACTION
fields will be executed at each new option; if you move back down the
branch toward the Primary Menu trunk they will not. See [EXIT ACTIONS]
and [HEADERS], because they will.
If, after an ENTRY ACTION has been executed, the variable XQUIT is
found in the partition, then the Menu System passes control to the XQUIT
Processing Software described elsewhere. Only after the ENTRY ACTION is
run does the Menu System check for XQUIT, and setting it elsewhere is not
Each option in the Option File has several fields of executable M
permitted or advised.
(a.k.a. MUMPS) code associated with it that are executed or run under
specific conditions. The ENTRY ACTION Field is one of these and it is
executed each time a new option is pushed onto the user stack. From the
user's view this means each time an option is invoked -- whether by the
selection from a menu, called "stepping into an option", or by jumping to
the target option -- this field is executed.
|
