Updating ui from thread c
The Operator Interface can then perform actions in response to this UI message, such as refreshing the execution window control to show updated step results.
Each UI message contains the following data relating to the execution event: In the Default Test Stand UI Messages section of this article, More detail is provided on the UI messages sent by the Engine by default.
These messages are used by the User Interface to obtain information about the state of the execution.
The Test Stand engine defines several message types (specified by the message ID), and automatically posts UI messages when these events occur.
Whenever this step executes, the thread will post a custom UIMessage (ID 10,001) which passes the string value of Parameters. Back to Top Within the sequence editor or a Test Stand Operator Interface, the Application Manager automatically acknowledges UI messages, and handles default UI message events.
However, we can configure the operator interface to run user defined code when a UI message is handled by adding an event callback for one of two Application Manager events: The implementations for handling custom UI messages in Lab VIEW and Lab Windows/CVI are explored in more detail in the next sections.
For example, the Test Stand engine posts a UI message to notify the Operator Interface when a step has completed.In some cases, you may need to notify the Operator Interface of additional execution events, or pass custom data to the User interface.