Message Trace
Message Tracing
Message tracing lets you create a history of messages. Since messages are really procedure and function calls, a message trace can be thought of as a call stack history. Messages are displayed in a tree view hierarchy.
The Message Trace window supports various operations through its context menu, accessed by right-clicking in the Message Trace window.
Trace Messages
This option starts and stops the message trace. A checkmark indicates that a trace is in operation. After you have started the trace, you should return to your program and execute the event or events you wish to trace. Do not leave the message trace running once you no longer need it, as it will slow down your debugging process and consume resources.
Clear Trace
Clears the Message Trace tree view.
Filter
This option lets you quickly add a message to the filter and suppress future occurrences of a specified message. Select the message you wish to filter, right-click, and select the Filter menu option. This adds the specified message to the list of filtered messages.
Filter Options...
Brings up the Message Trace Options dialog, which lets you add or remove messages to be filtered.
Save Trace
This saves the complete message history. All nodes are fully expanded, providing a complete record of your history trace.
When a trace file is saved, it is written to a file in your workspace's Programs folder with the name of your program followed by "_TraceLog.trc". For example, "Order_TraceLog.trc".
Save Trace as is
This saves the message history at the current expansion level. If a message trace is not expanded in the trace window, it will not appear expanded in the saved file.
When a trace file is saved, it is written to a file in your workspace's Programs folder with the name of your program followed by "_TraceLog.trc". For example, "Order_TraceLog.trc".
Message Trace Toolbar
Toggle Message Tracing
Click this button to turn on/off debugger message tracing.
Clear Message Trace
Click this button to clear the message trace panel.