Selection of Menu Buttons and Exiting from Menus

In Prompted, Scroll and ViewText Modes, the User must select Menu Buttons from the keyboard. Furthermore, several of the Menu Types (Toggle, Integer, Real, Mixed and Text) remain within the context of the Menu until the User indicates that all selections are completed and that he wishes to accept them. In Graphics and ViewCursor Modes this is indicated by movement of the cursor to the appropriate Button and ``clicking" on it, but the keyboard must be used for other modes. The syntax is:-

1. A Button may be identified by its Decimal number (being in the range 1-256).
2. A Button may be identified by the first word within the corresponding Descriptive Text (or that portion that results in an unambiguous match).
3. For Action Menus only, a Button may be identified by a response having a valid response Verb. In this case, the typed response replaces the response text associated with any Button on the Menu. Where the Descriptive Text on a Button conflicts with the Response Text, the Response Text takes presidence. Thus care should be taken for clashes.
4. Where the Button has an associated Value, the syntax:-

   <Button>=<Value> <Button> <Value> ...
   

   where <Button> is the Button Identification as described above, and <Value> is the associated Button Value. Several Buttons may have their values set on the same input line by separating them (and any associated value specification) by spaces or commas.

1. In order to reset all Buttons Values back to their original values, RETRY may be typed as a response. In situations where this clashes with the Descriptive Text on any Button, this reset function will take presidence and such Buttons may only be referenced by their Button Number. The Application Programmer may choose another word of up to 8 characters in length (containing no embedded spaces or tabs) in place of RETRY if so desired. The string RETRY (which may be truncated to R) is a valid alternative to RETRY and may be used at all times (it is not changeable by the Application Programmer).
2. In order to accept the present Values associated with all Buttons, OK may be typed as a response. In situations where this clashes with the Descriptive Text on any Button, this exit function will take presidence and such Buttons may only be referenced by their Button Number. The Application Programmer may choose another word of up to 8 characters in length (containing no embedded spaces or tabs) in place of OK if so desired. The string OK (which may be truncated to ) is a valid alternative to OK and may be used at all times (it is not changeable by the Application Programmer).