10-01-2005 04:34 AM
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 - 2022)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)
10-10-2005 06:21 AM
10-10-2005 07:30 AM
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 - 2022)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)
10-18-2005 05:06 PM
There is no way to prevent TestStand from breaking in given locations. However, if you are using an OI, it is possible to automatically continue executing until you reach a sequence context where Tracing is enabled. The execution will continue running (even if this takes a long time) until it reaches a point where you have tracing enabled.
To do this, you will need to add an Event Callback for the ExecutionViewMgr.Break Event. It will give you three parameters. You will get the property SequenceContext.Tracing from the ctxt parameter. If this is true, then we do not need to do anything. If it is false, we want to call the Execution.StepOut method on the exec parameter. This will finish execution of the current sequence, and try to break on the calling sequence. This will call the Break Event, so the process automatically repeats until it gets to a point that it is allowed to break. The downside is you will see all of these steps executing until the "real" breakpoint is reached.
11-15-2005 01:38 PM
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 - 2022)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)