I'm having an odd problem with the 'Execution.Break' method when runnning a sequence in our custom LabVIEW based GUI.
When we run from within TestStand, the Break method correctly pauses the sequence. When we run from our custom GUI, it seems to trigger the Abort method as the standard Abort dialog pops up asking how we want to handle the Abort and the sequence does not pause.
This seems to have just started happening in the last week or so. We're seeing the problem on three different machines.
Using LabVIEW and TestStand 2014 SP1 on Windows 7 Enterprise.