12-07-2006 11:36 AM
12-08-2006 08:43 AM
Pass in the SequenceContext and then you can get the execution from that. Or just pass in SequenceContext.Execution. You may have to change it to a variant.
Regards,
12-08-2006 11:46 AM
12-08-2006 01:58 PM
Hey Snood,
After you get the Obj Handle for the Execution are you converting it to a Variant before passing it to the set step mode call? Try:
CA_VariantSetObjHandle
Then you can pass it into the TS_StepSetRunModeEx
Regards,
12-08-2006 02:04 PM
12-08-2006 03:18 PM
Here is some code that should do the trick:
void __declspec(dllexport) setStepExec(CAObjHandle step, CAObjHandle context)
{
VARIANT execVariant;
LPDISPATCH execDispatch;
int error = 0;
CAObjHandle execObj;
TS_SeqContext
ERRORINFO errorInfo;
TS_SeqContextGetExecution (context, &errorInfo, &execObj);
CA_GetDispatchFromObjHandle (execObj, &execDispatch);
execVariant = CA_VariantDispatch (execDispatch);
TS_StepSetRunModeEx (step, &errorInfo, "Skip", execVariant);
Error:
if (error < 0)
{
}
}
There are probably memory leaks however but that is the gist of it.
Regards,
12-08-2006 06:27 PM
12-13-2006 04:25 PM
12-14-2006 03:10 PM
12-14-2006 03:39 PM
Hey Snood1,
The ObjectHandle would be the sequence context passed from TestStand into CVI. Basically it contains all the information about the state of the current execution. You should have an example that shows how to get the sequence context into your dll: <TestStand>\Examples\AccessingPropertiesAndVariables\PassingSequenceContextToDLL It was written in CVI so it demonstrates what you are looking for.
I hope this helps. Let me know if there's anything else.
Regards,