Click the Step button when you want to step through the code one statement at a time. Typically, each time you click Step, the system executes a single statement. The behavior may vary, however, in certain contexts.

As you step through a statement block or event block, the Debugger stops on the end statement that closes the block. This enables you to examine the results of the operations performed in the statement or event block.

When you step out of an event block, control returns to the application until another event occurs for which there is an event block. At this point, you may need to interact with the application to cause an event to happen. However, having stepped out of an event block, the Debugger stops at the first statement of the next block to be executed.

If you step into a statement that opens a pop-up dialog, the application has control until you close the pop-up.

If the next statement calls a frame or procedure, the Step button steps across the call; that is, the application receives control until the call completes. Control returns to the statement immediately following the call. If an intervening break condition is encountered before the call completes, the Debugger gains control. When the call does complete, however, the Debugger stops execution at the statement following the call statement.

Finally, if the statement is a gotoframe statement, clicking Step moves you to the script for the frame invoked by the gotoframe statement.