Known Issues - Adobe 12001196 - Acrobat - Mac Manual

Acrobat JavaScript Debugger
3

Known Issues

F
IGURE
Known Issues
Due to some limitations in the JavaScript Debugger, debugging of certain classes of scripts
in Acrobat is disabled or unavailable. Fortunately, there are plenty of other places and
situations where scripts can be debugged, so that your script can be tested and then
transported to its definitive place in case debugging is unavailable. Below is an incomplete
list of issues we have found during testing and development of the JavaScript Debugger in
Acrobat 6.0.
Menu-item scripts cannot be debugged or reached via the "Debug From Start" menu
option. You'll notice that if the "Debug From Start" menu item option is checked on, menu
items created via the JavaScript method app.addMenuItem() will be disabled. The correct
way to debug these scripts is to put a breakpoint on the function called from the "cExec"
parameter defined in the respective addMenuItem() call. This function may exist either in a
Config.js file, or in a doc-level script, both available for perusal and setting breakpoints via
the debugger dialog.
When trying to debug scripts at PDF file open time (e.g.: Doc-Level scripts) by turning on
the "Debug From Start" menu item option, other scripts may be triggered while we're
stopped in the debugger (e.g.: Page 1 Open scripts). The posterior execution of these
scripts may be incorrect, especially if they depend on definitions contained in the halted
doc-level script being debugged.
52
3.11 Second Runtime Error
Acrobat JavaScript Scripting Guide