Frame definition file descriptors

Menu, form, and text frame definition files have similar rules governing the order in which descriptors are defined.

frame descriptors

Descriptors that apply to the frame as a whole must be defined first. There can be only one set of frame descriptors in a frame definition file. Each frame descriptor should be defined only once. If defined more than once, then the last instance of the descriptor in the set is used. Frame descriptors that are out of order, that is, any that follow item, field, or SLK descriptors in the frame definition file, are ignored.

item or field descriptors

Descriptors that apply to an item in a menu or a field in a form must be defined next. There can be multiple sets of item descriptors in a menu definition file, and multiple sets of field descriptors in a form definition file--as many sets as there are items or fields. In each set, however, each item or field descriptor should be defined only once. If defined more than once, then the last instance of the descriptor in the set is used.

Text frame definition files do not have an equivalent to item or field descriptors.

screen-labeled function key (SLK) descriptors

Descriptors that apply to screen-labeled function keys (the name that appears on the screen label as well as the function assigned to the function key) must be defined last. There can be multiple sets of SLK descriptors--as many sets as there are SLKs you are defining. In each set, however, a descriptor should be defined only once. If defined more than once, then the last instance of the descriptor in the set is used.

The following tables summarize the available descriptors for each type of frame. They also show the default value of each descriptor, the type of string expected as a value, when the descriptor is referenced, and when it is evaluated by default. (See ``Frame definition files'', and ``Application level definition files'' for discussions of what these descriptors do and how to use them.)