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 the
    Interval
    property. Use
    Select Case
    or
    If Then Else
    logic combined with changes to the
    StepIndex
    property 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 the
    TerminateState
    method.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal