INTEGRATING THE SCRIPTEASE DEBUGGER
The ScriptEase debugger can be used to debug scripts being run in your ScriptEase:ISDK application. This section explains the steps you need to take to enable debugger support in your application.
There are two basic ways a debugging session can operate. First, your application may wish to connect to the debugger and debug a script. For instance, you may have a menu option to debug a script. In this case, your application runs normally until the time you wish to debug a particular script. When that debugging is complete, your application continues as normal. The second way to initiate debugging is by the command of the debugger. Typically, the ScriptEase IDE is being used to edit a script meant to be run by your application. When the user wants to try the script out, your application is invoked in the background to execute the script. Your application recognizes this situation by the presence of a /debug command-line switch. The rest of the command-line consists of the script to be run and any parameters to be passed to the script.
In either case, ScriptEase API calls are provided to establish a connection with the debugger and execute the script under the debugger's control. The connection between an application and the ScriptEase debugger is a TCP-IP socket. Connections can be established remotely, when the application and debugger reside on different machines.
THE CONTINUE FUNCTION
THE AT ERROR FUNCTION
INVOKING THE DEBUGGER
INVOKING THE DEBUGGER ON AN ERROR