Execution Class Reference

[Dia]

Hello,

I have been playing around with TS UI controls for a bit now but have the need to get into the nitty gritty of things. I want to know how to create references to the Execution class (and other classes) from these UI controls I am using.

Thank you,

Dia

[AllenP]

Dia,

There are several methods to get execution references.

For instance, if you want the currently selected execution, you can use ExecutionViewMgr.Execution.

Also, you can create new executions from ApplicationMgr.GetEngine, and call Engine.NewExecution.

Is there something specific you are trying to do? There are many ways that the TestStand API and the TestStand UI Controls API are related, and this can be found in the TestStand UI Controls API.

Allen P.

[Dia]

Well, what I am trying to do is make use of the methods from the Execution class given the manager controls. I will try to use the Execution property in ExecutionViewMgr and I am guessing I can use that to reference the methods I want?

[AllenP]

You can use those methods, as long as you have an execution object. The execution object is not creatable (you must get it from some other object, such as the engine, or the ExecutionViewMgr).

If you get stuck, let me know what you are trying to do.

[Dia]

This might be more of an MFC question than a TestStand one. I am not sure as I am new in both.

I am playing around with the example in \OperatorInterfaces\NI\Simple\C++ using MFC. I wish to be able to invoke methods from the Execution Class from a 'main' type function after the dialog box is loaded. Is it possible?

[Dia]

A bit more detail into what I wish to accomplish:

-have the example application I mentioned in my previous post load up, and
-have some loop run in the background and load seq. files and run them (this part I know how to do using the TS OI & API)

Any help would be greatly appreciated.

[AllenP]

One of the first functions that get called is "OnInitDialog". Once it completes, the program is executing in a message loop and waits for callbacks.