Indicates the orientation of a scroll bar form field.
Valid Values
An integer code, as shown in the table below:
Code | Meaning |
1 | Vertical |
2 | Horizontal |
A collection of tables describing all objects needed to build a Zim:X application.
Indicates the orientation of a scroll bar form field.
An integer code, as shown in the table below:
Code | Meaning |
1 | Vertical |
2 | Horizontal |
A user-assigned numeric identifier for the form field.
An integer (0 to 999)
If no number is assigned, 0 is used.
FNum can be used in an application program to identify the form field that had focus when control returned to the program. (See $FieldNum, $MenuItemNum, and $MouseFieldNum in the Language Reference.) For form fields with no transmit attributes, FNum is usually left at 0 unless the BY FIELDNUMBER option is to be used to set the tab order (see the WINDOW SET TABORDER command in the Language Reference).
FormNum, MenuNum, WNum
Case conversion status of a form field. Indicates how alphabetic characters typed into the form field are to be treated.
A 1-character code, as shown in the table below:
Code | Meaning |
M | Mixed case (characters will appear exactly as entered) |
U | Upper case (characters will be converted to upper case) |
L | Lower case (characters will be converted to lower case) |
The value of a toggle button or menu item. Specifies the value of a toggle button or menu item in the OFF, ON, or NULL states.
A 256-character string
If the toggle object has no ValRule, then WdgOnValue is used to determine whether the object is set “on”. (The object is “on” only if its current value exactly matches the WdgOnValue.)
If “allow nulls” is off (AN = N), then a toggle button may never exist in the null state.
Menu items are not permitted to exist in the null state.
AN, ValRule
“Drop target” status of a form field. Indicates whether a form field can have a dragged form field dropped on it.
An integer code, as shown in the table below:
Code | Meaning |
N | (DEFAULT) No |
Y | Yes |
The masking pattern used when data is input into the entry field.
A 256-character string, defining an input mask for the field.
The input mask is applied only when the form field is available (unprotected) and has focus.
When the field loses focus, the input mask disappears; if a display mask (DataMask ) is available, that mask is then applied.
For a more detailed explanation of mask patterns and their relation to data types, see Masking.
Compress status of a form field. Indicates how the data mask associated with the form field is to be treated.
A 1-character code, as shown in the table below:
Code | Meaning |
Y | The data mask literals are not included in the value of the form field |
N | The data mask literals form part of the value of the form field |
Form fields with data types (DT) of numeric and date force a compress status of Y.
DataMask, DT, WdgInputMask
Indicates whether a text-entry form field consists of one line or multiple lines.
An integer code, as shown in the table below:
Code | Meaning |
0 | One line |
1 | Multiple lines |
WdgNumVisibleLines
“Allow nulls” status of a form field. Indicates the value to be taken by the form field when it contains no data.
A 1-character code, as shown in the table below:
CODE | MEANING |
Y | When no data is entered, the field is $Null (valueless) |
N | When no data is entered, the field takes the value zero (0) if its data type (DT) is numeric or date, or the null string (“”) if its data type is alphanumeric |
When AN is set to N, the end-user can set a toggle button to the null state.
DT
Indicates how the form field responds to a GotFocus event (“transmit-on-enter” status).
A 1-character code, as shown in the table below:
Code | Meaning |
N | No response except to visually indicate GotFocus (DEFAULT) |
Y | Control returns to the application program every time the form field gets focus |