NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Connect the executions to their ExecutionViewMgr's in parallel tests

Hi,

Isn't there a more elegant solution to connect the executions to their ExecutionViewMgr's than this way (proposed by Tyler), se below ? 

This way you have to send a UI message from a separate step in the sequence for each execution.

case UIMessageCodes.UIMsg_UserMessageBase: //Connect each execution to their ExecutionViewMgr

switch ((int)e.uiMsg.NumericData)

{

case 0:

axExecutionViewMgr1.Execution = e.uiMsg.Execution;

break;

case 1:

axExecutionViewMgr2.Execution = e.uiMsg.Execution;

break;

.
.
 
 
 
0 Kudos
Message 1 of 2
(2,946 Views)

FYI

Moved it to the axApplicationMgr_DisplayExecution callback function. Now I don't have to send a UI message from a separate initial step in the sequence for each execution.

int frameId;

int executionID;

SequenceContext seqContext = e.exec.GetThread(0).GetSequenceContext(0, out frameId);

executionID = seqContext.Execution.Id;

switch (executionID)

{

case 3:

   axExecutionViewMgr1.Execution = e.exec;

break;

case 4:

   axExecutionViewMgr2.Execution = e.exec;

break;

.

.

 

0 Kudos
Message 2 of 2
(2,930 Views)