1. Basic rule
2. Logic segment
3. Select operations without corresponding controls on Form
4. How Flow direction determines the conversion process
1. Basic rule
All operations between Select operations, with corresponding controls, are converted into Control Verification handler on first control.
Here is simple example how RM Compatible Logic is converted into event-driven mechanism:
RM Compatible logic:
Converted to event-driven mechanism:
Each Verify Error operation is converted into the appropriate Control Verification event, with all the properties.
2. Logic segment
Conversion process first determines logic segments. Logic segment is all operations between two consecutive Select operations, with corresponding controls on Form.
RM Compatible logic:
Converted to event-driven mechanism:
3. Select operations without corresponding controls on Form
Select operations which are not represented as controls on Form, are skipped, if they are between two controls:
RM Compatible logic:
Converted to event-driven mechanism:
Variables vTempVarA and vTempVarB are not on the form as controls, so the Call Program 97 operation is part of the logic segment between 'Customer Name' (A) and 'Customer Status' (D).
In this case the conversion process takes this operation as part of logic segment between 'Customer Name' (A) and 'Customer Status' (D), and converts it accordingly.
4. How Flow direction determines the conversion process
Operations are converted by rules, which the flow and directions are changed accordingly to new event-driven mechanism...
RM Compatible logic:
Converted to event-driven mechanism:
Current RM Compatible behavior:
When cursor moves from 'Customer Name' (A) to 'Customer Status' (B) then Verify 'Forward' and Verify 'Combine' are executed. When we move backward from 'Customer Status' (B) to 'Customer Name' (A), then Verify 'Backward' and Verify 'Combine' are executed.
To keep the same engine flow, these are the rules for conversion:
a) All operations in Forward and Combine direction are converted to Verification handler to ControlA (first Select operation with corresponding control on form)
b) All operations in Forward and Combine direction are converted to Verification handler to ControlB (second Select operation with corresponding control on form) in reversed order
NOTE: A setting 'Convert operations with Combine direction in Verification to: Forward/Backward/Both' determines how operations are converted, depending on their Flow direction.