Using multiple dialogs / Procedural DIALOG block configuration |
By default, the form tabbing order is defined by the variable list in the binding specification. You can control the tabbing order by using the FIELD ORDER FORM attribute; when this attribute is used, the tabbing order is defined by the TABINDEX attribute of the form items.
The field order mode can also be specified globally with the OPTIONS FIELD ORDER instruction.
With FIELD ORDER FORM, if the user changes the focus from field A to a distant field B with the mouse, the dialog does not execute the BEFORE FIELD / AFTER FIELD triggers of intermediate fields which appear in the binding specification between field A and field B. Unlike singular dialogs, if the default FIELD ORDER CONSTRAINT mode is used in a multiple dialog instruction, intermediate triggers are never executed (i.e. the Dialog.fieldOrder FGLPROFILE entry is ignored by DIALOG.)
See also Defining the tabbing order.
The UNBUFFERED attribute indicates that the dialog must be sensitive to program variable changes. When using this option, you bypass the compatible "buffered" mode.
The unbuffered mode can be set globally for all DIALOG instructions with the ui.Dialog.setDefaultUnbuffered() class method:
CALL ui.Dialog.setDefaultUnbuffered(TRUE) DIALOG -- Will work in UNBUFFERED mode ... END DIALOG