PC-based phase events
The phase programmer must follow certain conventions when using Visual Basic and the
Batch Phase Execution
control:
- NEVER use modal dialog boxes or other user interface that causes the program logic to wait at some point. This can prevent the PLI from responding to state changes.
- NEVER use looping logic that waits at some point. This can prevent the PLI from responding to state changes. The PLI runs every X millisecond as specified by theIntervalproperty. UseSelect CaseorIf Then Elselogic combined with changes to theStepIndexproperty to advance from section to section within your code.
- The phase programmer is responsible for transitioning the phase from an active state (RUNNING, STOPPING, and so on) to a finished state (COMPLETE, STOPPED, and so on) using theTerminateStatemethod.
Provide Feedback