Adobe 65036570 Scripting Guide - Page 127

ADOBE DIRECTOR 11.0 90 Scripting Dictionary Run nested handlers one line at a time Click the Step Into Script button in the Debugger window. Clicking the Step Into button runs the current line of code and follows the normal flow through any nested handlers called by that line. When finished with a nested handler, the Debugger window stops at the next line of code within the upper-level handler. When you are finished debugging, you can exit the Debugger at any time. Resume normal execution of code and exit the Debugger window Click the Run Script button. Exit the Debugger and stop playback of the movie Click the Stop Debugging button. Editing scripts in debugging mode When you are in debugging mode, you may edit your scripts directly in the Debugger window. This enables you to fix bugs as soon as you find them and then continue debugging. Edit a script in the Debugger window 1 Click in the Script pane and place the insertion point where you want to begin typing. 2 Enter the changes to the script. You can jump to a specific handler by selecting the name of the handler and clicking the Go to Handler button. 3 When you are finished debugging and editing scripts, click the Stop Debugging button. The Script window returns to Script mode. 4 Click the Recompile All Modified Scripts button. Debugging projectors and Shockwave movies This section discusses debugging during runtime in Director projectors and movies that contain Adobe® Shockwave® content. You can use either the Message window or enable full script error dialog boxes to debug projectors and movies that contain Shockwave content. Debug using the Message window Set the Player object's debugPlaybackEnabled property to TRUE. When this property is TRUE, playing back a projector or a movie that contains Shockwave content opens a Message window (Windows) or a Message text file (Mac), and the results of any put() or trace() function calls are output to these formats. If at any time during the movie the debugPlaybackEnabled property is set to FALSE, the Message window or text file is closed and cannot be opened again during that playback session, even if debugPlaybackEnabled is set back to TRUE later in that session.