OutputDebugString(PChar('Quality Suite:TRACING:ON'));

[tfield98]

The help system says:

When using trigger mode, tracing doesn?t start until a trigger routine executes. However, you may control the tracing from within your module by issuing calls to the standard Win32 API function OutputDebugString. Passing the argument "Quality Suite:TRACING:ON" switches tracing on and the argument "Quality Suite:TRACING:OFF" switches tracing off from within your code

I haven?t been able to get this to work.

My small test program traces fine if I set ?Always on? in the tool bar.

But if set the field to Trigger Activated?, I get no tracing after the code executes the line below:

OutputDebugString(PChar('Quality Suite:TRACING:ON'));

Any suggestions on what I might be doing wrong?

[Eivind]

Originally Posted by tfield98

The help system says:

I haven?t been able to get this to work.

My small test program traces fine if I set ?Always on? in the tool bar.

But if set the field to Trigger Activated?, I get no tracing after the code executes the line below:

OutputDebugString(PChar('Quality Suite:TRACING:ON'));

Any suggestions on what I might be doing wrong?

I'm sorry, it appears the help file was out of sync with the tools. For most of the tools, the exact strings to use are

NQS:TRACING:OFF
NQS:TRACING:ON

The only exception to this is the Method Timer, which replaces NQS above with METHODTIMER. I will change that for the next release to make all tools use the same NQS string, and update the help.

[tfield98]

In a small test program, Method Timer works fine when run with Mode set to Always On.

However, when I run it with Trigger Activated, even after the two lines below being executed, I get no trace

outputdebugString(PChar('METHODTIMER:TRACING:ON'));
outputdebugString(PChar('NQS:TRACING:ON'));

Any suggestions on how to activate a trigger in the code in Version 1.6001?

Thanks.

Tom

> PChar('METHODTIMER:TRACING:ON')

Sorry about the delay. Having done a test, it appears the above does
turn tracing on and off (you can see one line which changes in the
trace grid). However, there's only ever that one line, so there is a
problem getting a trace result. I will investigate and fix.

--
Eivind Bakkestuen [NDD]