Full Tracing

Turn tracing on if you want to examine the full flow of execution. Tracing imposes a significant overhead on the system unlike the stack trace, which shows only the active functions. Depending on the trace level required, Dashboard Studio can keep track of all calls made which are then available for output to Notepad by using the command; for example

ActiveDocument.Sections["QIQ Diagnostics"].Shapes["cbtTrace2Txt"].OnClick()

The history is kept in a list which increases in size until tracing is turned off or the dashboard is closed. If a dashboard is saved and closed with tracing on, tracing resumes when it is reopened.

These commands can be made part of the Custom menu environment to turn tracing on and show the tracing window:

var x=ActiveDocument.Sections["QIQ Diagnostics"];
x.cbxTraceOn.Checked=true;
x.cbxTraceOn.OnClick();
if(!x.Visible){x.Visible=true;x.Activate()}

These commands can be incorporated into the Custom menu environment to turn tracing off:

var x=ActiveDocument.Sections["QIQ Diagnostics"];
x.cbxTraceOn.Checked=false;
x.cbxTraceOn.OnClick()