ArborX

trace

Longname: trace   Open the Documentation Legend
Released: not available 
Created: not available 
See also: boxit

Summary
 Debugging even quite simple scripts can be made easier using the trace macro. This lets you process scripts line-by-line, changing commands as and when necessary. Although it should rarely be necessary to trace the whole of a script, problem areas can be enclosed within a trace 1 ... trace 0 sequence, and traced until you find the source of the problem.
Example (n/a)
 No example is available for this feature.

Syntax (SVNNA)
trace Ø
trace  option:n?
Ø Displays the Macro Tracer dialogue box.
Ø:

The Macro Tracer dialogue box displays the current macro; you can click the Simple button to reduce the number of options shown in the dialogue box.
option:n
1  Trace on.
2  Trace off.
The main reason for scripts not behaving as you expect is that one of the special characters required has been specified in the wrong way. Some of the other things that might prevent a script from working properly are listed below:

Script crashes Arbortext APP: There may be a wmn macro invoking a menu that has not been defined, or has been wrongly defined.

Script crashes Arbortext APP: Very long menu lines can crash Arbortext APP.

Script crashes Arbortext APP: A wmn macro may have been used instead of wdb by mistake (and vice versa).

Script Trace Avoidance Syntax

Version specific information7.76a  When using the "trace 1" script tracing macro, all script calls are run through the tracing system - this includes dialogue [[scripts]] syntax. By adding an exclamation mark as the first character after the opening [[ of a script line, or [ of an update alias code, the script is run non-traceable, for example:

 update (^21020) [!5] 1
 apply 5 [[! 2
 boxit "You can't trace me!" 3
 ]] 4

Document created on 08-Feb-2003, last reviewed on 09-Jul-2003 (revision 2)