2020.1

PCL, PDF, PNG, PS, SVG, and TIF/TIFF.
Using the Script Debugger
The Designer's Script Debugger allows you to set breakpoints in scripts and step through them.
It simulates an output run with only the current record and shows an overview of the state of all
local and global variables, while the Workspace displays the partially merged document.
There are two ways to start the Script Debugger:
l
Click the Debug Scripts button in the toolbar of the Scripts pane. The Script Debugger
will pause and accept input as soon as it processes the first script.
l
Right-click an enabled script in the Scripts panel and choose Debug from the contextual
menu. The Script Debugger will pause and accept input as soon as it processes the
selected script.
If the selected script is never processed, a message will pop up. This can happen when:
l The selector has no matches at any time. (This may depend on other scripts, since scripts
can add or remove content.)
l The script is excluded through the properties of its parent folder.
For an explanation of the buttons in the Script Debugger, see "Script Debugger" on page965.
Testing for speed issues
To measure the time that the execution of scripts will take:
l
On the Context menu, click Profile scripts.
Profiling means running the scripts in the template, with the current record, to see how fast
scripts in the Scripts pane execute. It helps greatly in troubleshooting performance issues
caused by scripts.
After running the Script Profiler you can see in which sections the script has run:
Page 856