Hi,
I am using a different approach suggested at one of NI's Best Practices article-
(It works great, so I thought I would share that....)
Best Practices for NI TestStand User Interface Development
http://www.ni.com/white-paper/7560/en/
See the section:
"You can also use a synchronous technique that utilizes a UIMessage that originates from the test. For example, you can modify the process model to post a UIMessage during initialization and pass the SequenceContext (or other object) to the user interface. When you post the UIMessage, set the synchronous parameter to True so that the execution waits until the user interface processes the message. When the user interface processes the UIMessage, it retrieves the SequenceContext object and writes or reads certain variables, such as the process model local variables. This way, the user interface can pass data back to the message sender, depending on your particular needs regarding the preferred method to pass data from the user interface to the test."
