How to I do TestStand engine control for VB MDI structure?

[viko]

How to I do TestStand engine control for VB MDI structure?

I owns two sequence files,but I don't know how to call TestStand engine control for VB MDI structure!

Please to see I attachments file.
Please give me some suggestion.
Thank's everyone!

[RayFarmer]

Hi,

Good place to start would be to study the VB Operator Interfaces.
Try download the Simple VB Operator Interface which is the bear minimun required the run your sequence files.

http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3EF0556A4E034080020E74861&p_node=DZ52205&p_source=external

Hope this helps you to get started
Regards
Ray Farmer

[viko]

Dear Ray,

Thank's you answer.

This a example I already try,but this example is single,I want to MDI structure,
Could you show me an example for illustration?

My address mail is vikoyang@hotmail.com

Thanl's everyone!

[Jason F.]

Hi Viko,

The key to understanding how to create an MDI Operator Interface is described in my post to your previous question on the same topic here:

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000049850000&ECategory=TestStand

We do not have an example of a VB MDI OI appilcation, but as Ray pointed out most of the code necessary to create a VB OI can be found within TestStand's shipping OI examples. The only real difference between these examples and your MDI application is where the TSEngine control is located and how you would access the Engine object's properties from within code pages for child forms.

These topics are explained concisely in my reply to your previous post, but it should be realized t
hat this is not a unique topic to programming with TestStand and the exact issues you are inquiring about can be found in virtually all VB MDI applications. The main premise behind what you are asking can be generalized as "How do I access an ActiveX control's properties/methods on the MDI parent form from a child form?" For further VB MDI programming topics you should refer to the Microsoft Developer Network for further examples on accessing parent form object's and the like:

http://msdn.microsoft.com

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask

[viko]

Hi Jason,

Thank's a lot ,I decide to select your suggestion,but I don't know how to use the
"parentForm.Engine1.NewExection clientSeqFile,MainSequence,paralleModel,False,0"
or you can mark a section about the NI's document to me that I can seach the data soon.
And What the meaning of the "clientDeqFile" and "MainSequence"?

Could you help me?
Thank's everyone.

[Jason F.]

Hi Viko,

The line of code I gave was an example of accessing the TestStand engine control located on the parent form of your MDI application so that you could call the engine object's methods, just as you would in any other operator interface application (like the Visual Basic Operator Interface that comes with TestStand that I suggested looking at to better understand how to do these types of things). To clarify the following line of code:

parentForm.Engine1.NewExecution clientSeqFile, MainSequence, parallelModel, False, 0 ' This will launch a new sequence execution

Consider these definitions for the members of the code snippet:

parentForm = the object name of your parent form
Engine1 = the object name for the TS engine control
on the parent form
NewExecution = a method of the TS engine that launches a new sequence execution

*The rest of the items in the line of code are parameters to the NewExecution method.

For more information on using the NewExecution method you should reference the TestStand Programmer Help Manual (in the Sequence Editor select Help >> TestStand Programmer Help). To better understand how to write code like that given above to create a proper TestStand operator interface application in Visual Basic you will have to look at the examples come with your TestStand installation under the \OperatorInterfaces\NI\VB and \Examples\OperatorInterfaces\Simple VB (Note: these are two different operator interface applications. The OI in the first directory is a full featured version, whereas the second one is a simple OI that has the minimal features needed to implement an OI).

Jason F.
Applications Engineer
National Instruments
www.ni.com/ask