vsTASKER 7 User Manual
×
Menu
Index

Properties

 
Properties
1

If

1. If
Contains the condition to trigger the Rule.
This condition is a C/C++ expression that is true or false. It is not a function, it is an expression.
 
2

Then

2. Then
Contains the code that is run if the condition (1) of the rule is true.
The user can put whatever C/C++ code he wants there. This code can access all vsTASKER API, all included third-party APIs and all user designed scenario, entity, knowledge and context data of the current database.
 
3

Else

3. Else
Contains the code that is run if the condition (1) of the Rule is false.  
The user can put whatever C/C++ code he wants there. This code can access all vsTASKER API, all included third-party APIs and all user designed scenario, entity, knowledge and context data of the current database.
This part is optional and can be left blank.
4

After Fire

4. After Fire
Selection box to decide what to do with the Rule once it triggers (evaluates to true):
 
  • Rule is Done: Once triggered, the Rule is not revaluated again until the Context is reset.
  • Reactivate Rule: Once triggered, the Rule is evaluated again at next Context cycle.
  • Reactivate Rule After: Once triggered, the Rule is evaluated again after a time delay specified in the next field.
  • Reactivate Context: Once triggered, the Context is reactivated, meaning, all fired rules are reactivated.
  • Reactivate Context After: Once triggered, the Context is reactivated after a time delay specified in the next field.
  • Exit Context: Once triggered, the Context is exited. If an Reaction has been set in the Context property window (On Exit), it will be triggered.
  • Exit Knowledge: Once triggered, the Knowledge is exited. All Context are terminated. The hand returns to the Behavior.
     
5

Help

5.
Any description of the Rule can be put here and will be used for the automatic document generation (see Make Documents)