724 Debugging Applications
Step Out advances the Debugger out of a function. This button works only if you are
currently stopped in a user-defined function; it moves the yellow arrow to the line after the
line where that function was called. In the previous example, if you place a breakpoint at
line 3 and click Step Out, the Debugger moves to line 8. Clicking Step Out at a line that is
not within a user-defined function is the same as clicking Continue. For example, if you stop
at line 6 and click Step Out, the player continues to execute the script until it encounters a
breakpoint.
Step Over advances the Debugger over a line of code. This button moves the yellow arrow to
the next line in the script. In the previous example, if you are stopped at line 7 and click Step
Over, you advance directly to line 8 without stepping through
myFunction(), although the
myFunction() code still executes.
Continue leaves the line at which the player is stopped and continues playing until a
breakpoint is reached.
Stop Debugging makes the Debugger inactive but continues to play the SWF file in
Flash Player.
Using the Output panel
In test mode, the Output panel shows information to help you troubleshoot your SWF file.
Some information (such as syntax errors) appear automatically. You can show other
information by using the List Objects and List Variables commands. (See “Listing a SWF file’s
objects” on page 726 and “Listing a SWF file’s variables” on page 727.)
If you use the
trace statement in your scripts, you can send specific information to the
Output panel as the SWF file runs. This could include notes about the SWF file’s status or the
value of an expression. (See “Using the trace statement” on page 728.)
To display or hide the Output panel, do one of the following:
■ Select Window > Output
■ Press F2.
To Next Page
Loading...