|
IfState Tag |
|
|
|
|
IfState Tag |
|
|
IfState Tag
|
IfState Tag |
|
|
|
|
IfState Tag |
|
|
The IfState tag is used to evaluate the user data entry and select the next screen and context based on the current context. The script evaluation will first try to find a perfect match between user entries and a potential starting context. If that doesn't work (user entries have a match but the context isn't correct), the context will be reset to match the entries and the IfState contents will be evaluated.
Note that IfState tags can be nested to accommodate the same data entry values occurring in multiple contexts. In this case, the data entry (changes) attribute will be the only attribute at the top level, and children tags will only have context to be matched.
Attribute |
Default / Required |
Description |
changes |
required for top-level, but not Child IfState tags |
Sets of row,column,value triplets defining user data entry. Format is [row],[column],[value] with semicolons separating the triplets. If a value has a semicolon inside it, it is quoted. |
context |
optional at top level, required in children IfState tags. |
The recording contexts that represent "from and to"--if the changes match user data entry, than the context is checked to determine the next step. If the current context (Recording+screen index) is matched, the next screen in the context pair is selected for display and context is set.
In a Child IfState tag, the context is used when the same data entry is found in many situations.
Note that context can have multiple possibilities that are carried forward, so that all recording contexts that match the current data entry can be evaluated in an ongoing basis. |
Child Tags Allowed: