Grass Valley Xpanel Vertigo Suite v.4.8 - Manual (Page 99)

Xpanel User Manual 5-13
Adding events and actions to primitives and objects
Adding conditions to an event’s action list
Adding a condition (If or If/Else) allows more sophisticated logic to be applied by evaluating
and then determining which actions are executed based on user-defined criteria.
When an I F condition is added to an event, the specified actions will only be executed when
the If condition is true. If the condition is not satisfied/true, then no action is executed. For
example, when the button primitive is clicked (On Click event), if the state on DSK keyer 1 is
up (If condition), then display the text “DSK 1 On” in a text box primitive (Set Text action).
Adding an Else statement below an If condition allows you to execute specified actions that will
be executed when the If condition is false. Building on the example above, if the DSK keyer 1 is
up (If condition), then display the text “DSK 1 On” in a text box primitive (Set Text action),
otherwise display the text “DSK 1 Off” in a text box primitive (Else statement & Set Text action).
To add and define an If condition:
1.
With the event selected in the Action Editor, click the A DD C ONDITION button.
2. Click the button in the D EFINE CONDITION row.
The Expression Builder window appears, which allows you to build the condition that
will be evaluated and must be true for the action(s) to be executed.
3. Using the Expression Builder, create the condition’s logic and then click OK.
When building condition statements and setting some properties or parameters (step 5),
Xpanel uses prefixes to specify the origins of objects and data. See
“Prefixes (Control:,
Data:, L:, G:)” on page 6-14 for more information on the prefixes that Xpanel uses to
identify objects and data.
4. Click and select an action from the drop-down list.
N
OTE
If the Action Editor’s standard actions do not perform the specific functions that you require,
you can select the C
USTOM action, which allows you to use scripts to define the desired logic
and behavior. See “Using scripts to define a custom action” on page 5-14 for more
information.
5. Set the action’s parameters which appear in the right-hand section of the Action Editor.
Note that when a parameter is selected, a brief description of the parameter appears
below the parameter list.
6. Optional: Click on the Action’s C OMMENT column and type a user-friendly description of
the purpose or behavior of the action.