![]() To advance execution from the current script location in a subroutine to the next statement in the calling function, click The Step Into button performs a Step Over action with all other statements. Step Over button will execute all the code contained within the subroutine and move to the next statement in theĬalling function, Step Into will advance script execution to the first statement within the subroutine body. The Step Into button is used when a statement containing a call to a user‐defined subroutine is reached. To advance execution into a user defined subroutine, click the Step Into button. When stepping through a statement containing a user‐interactive function call (such as GetPt() or GetLine()), theĭebugger dialog will be hidden and again will be shown after the function is executed. Which is stepped through is a user defined subroutine, all the code within the subroutine is executed. The script position indicator advances to indicate the new location of script execution. The Step Over button advances script execution by a single statement and refreshes the data display pane of theĭebugger. To execute a single statement in the script, click the Step Over button. Stepping Through a Single Line of a Script Using breakpoints, see VS:The_VectorScript_Debugger#Using Breakpoints. Running scripts is primarily used in conjunction with setting a breakpoint in the debugger. To continue the execution of the script until the script finishes or until the next break point, click the Continue Debug button. To run the rest of the script without debugging, click the Run button. The display is updated as execution proceeds, so that values can be continuously watched for changes duringĪrrays, elements, and structure members may be displayed by clicking on the disclosure triangle ( ) that appears next to The variable data display pane displays the current values stored in variables, arrays, and structures declared in the This arrow indicates the line of code that is about to be executed. The script is indicated by the small blue arrow ( )on the left‐hand side of the pane. The script source code pane displays the source code of the script being debugged. Subroutines are being called and the execution location within those subroutines. Each subroutine name appearsīelow the function calling it in the list by highlighting the desired subroutine name, it is possible to determine which The script calling chain pane displays the current function calling chain of the script. See VS:The_VectorScript_Debugger#Controlling Execution for details on controlling script execution in the debugger. With the script, script status information, or errors encountered in script execution. These messages may include prompts for user interaction The message area displays information about the script. ScriptĮxecution can be started, stopped, paused, or advanced one line at a time. The debugger controls allow the execution of the script to be controlled during the debugging process. The debugger window contains controls for managing script execution, as well as several areas for displaying variousĭata about the script and the state of execution. The script and the current state of execution. The debugger window is then displayed, providing a wide array of information on When the debugger is launched, storage for variables and constants is defined and script execution is paused at theįirst line of code in the script body. Line until the end of the script is reached. ![]() ![]() The debugger performs this task beginning at the first line of the script and continuing through each The VectorScript debugger allows a script to be executed in a line‐by‐line fashion, also known as ʺsteppingʺ through This launches the VectorScript debugger and displays the window as shown: Oval(x1 - radius,y1 + radius,x2 + radius,y2 - radius) This compiler directive, which canīe placed anywhere within a script, instructs the compiler to activate and display the debugger window when the The VectorScript debugger is activated by using the compiler directive. The script line by line to view the associated data, variables, and flow of script execution. Using the debugger, it becomes possible to locate and solve problems by moving through Known as a source‐level debugger, controls the execution so that the internal operations of the script can be observed VectorScript provides a powerful tool to assist in solving problems that may occur while developing scripts. 3.3 Stepping Through a Single Line of a Script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |