The Test Mode - Form Context dialog is displayed by clicking on the Form Context push button in the Test Mode - Event Vector dialog. This dialog presents the information contained in the Zim form context vector ThisForm which describes the status of the form or display (if any) when an event was triggered. The dialog consists of five sections: Event, Tags, Form, Validation Check, and Required Check.
This section presents information relating the identification of the event and is identical to that presented in the Event section of the Test Mode - Event Vector dialog.
| Event | Description |
| Name | This field contains the name of the event, and contains values such as "Click", "DoubleClick", "Modified", "LostFocus" etc. See Callback events for more detailed information about event names. |
| Type | This field contains the type of event that also identifies the type of object that triggered the event such as a "Window", "FormField" etc. See Callback events for more detailed information about event types. |
| Tag | This field contains the tag associated with the object that triggered the event. Each object type can have an associated tag in the form of a character string. If an object's tag is blank, the object's name is displayed in this field. |
This section presents information relating to the tags associated with the form field which either triggered the event, or had the input focus when the event was triggered by either a window or menu.
| Associated Tag | Description |
| Display | If a display is the currently open object within the window, this field contains the tag associated with the display, and if the tag is blank, the name of the display. If the currently open object within the window is a form, this field is blank. |
| Form | This field contains the tag associated with the form that either owns the form field which triggered the event, or owns the form field which had the input focus when the event occurred. If the form tag is blank, the form name is displayed. |
| Field | This field contains the tag associated with the form field that either triggered the event, or had the input focus when the event occurred. If the form field tag is blank, the form field name is displayed. |
This section presents information relating to the status of the form that triggered an event.
| Field | Description |
| Form Changed | This field is checked if the data content of the form has changed when the event occurred. |
| Field Changed | This field is checked if the data content of the form field that had the input focus has changed when the event occurred. |
| Form Number | This field contains the identifying number associated with the form that owns the form field which had the input focus when the event occurred. |
| Field Number | This field contains the identifying number associated with the form field that had the input focus when the event occurred. |
| Subscript | If the form field that had the input focus is owned by a form that has repetition instances within a display, this field contains the index into the repetition instances for that form field. Otherwise it contains the value 1. The index into repetition instances (and hence Subscript) uses 1-based ordinality. |
This section presents identifying information for any form field with an outstanding validation error when the event occurred. A validation error occurs when the data content of a form field does not satisfy the Validation Rule associated with the form field. Only the first such form field (in tab sequence order) is reported.
| Field | Description |
| Error | This field is checked if there exists a form field with an outstanding validation error. |
| Tag | This field contains the tag associated with the form field with the outstanding validation error. If the form field tag is blank, the form field name is displayed. |
| Form Number | This field contains the identifying number associated with the form that owns the form field with the outstanding validation error. |
| Field Number | This field contains the identifying number associated with the form field with the outstanding validation error. |
| Subscript | If the form field with the outstanding validation error is owned by a form which has repetition instances within a display, this field contains the index into the repetition instances for that form field. Otherwise it contains the value 1. The index into repetition instances (and hence Subscript) uses 1-based ordinality. |
This section presents identifying information for any form field with an outstanding data required error when the event occurred. A data required error occurs when the data content of a form field with has a Required attribute value other than "No" is blank. Note that only the first such form field (in tab sequence order) is reported.
| Information | Description |
| Error | This field is checked if there exists a form field with an outstanding data required error. |
| Tag | This field contains the tag associated with the form field with the outstanding data required error. If the form field tag is blank, the form field name is displayed. |
| Form Number | This field contains the identifying number associated with the form that owns the form field with the outstanding data required error. |
| Field Number | This field contains the identifying number associated with the form field with the outstanding data required error. |
| Subscript | If the form field with the outstanding data required error is owned by a form which has repetition instances within a display, this field contains the index into the repetition instances for that form field. Otherwise it contains the value 1. Note that the index into repetition instances (and hence Subscript) uses 1-based ordinality. |
| Button | Description |
| Close | This push button returns to the Test Mode - Event Vector dialog. |