Debugging

The GuiXT Script Editor Pro debugger is a powerful tool that allows you to step through InputScripts. It enables you to set breakpoints to pause the script execution at specific points and analyze its current state.

The debugger allows you to monitor variables in real time, verify their values, and track changes. It is specifically designed to efficiently identify and fix issues or errors in InputScripts.

Note: The debugger works exclusively with InputScripts, as they represent the logical programming layer in GuiXT. Standard GuiXT scripts that only modify the layout cannot be debugged.

Key features include:

Step-by-step execution: Execute the script line by line to analyze its flow.
Setting breakpoints: Pause execution at predefined points.
Variable inspector: View and monitor variable values during debugging.

The debugger provides an ideal foundation for analyzing complex InputScripts and optimizing their functionality.

If GuiXT is running and an appropriate SAP screen is open, the debugger can be activated by pressing the "Debug" button. This opens a dialog for monitoring variables.

Once an InputScript is started on the SAP screen, debugging is automatically activated. You can step through the script to analyze its execution.

Additionally, you can set breakpoints to pause at specific points and review the current state. You can also jump to any line in the script.

Breakpoints can be set or removed in several ways:

By clicking on the area to the left of the line number.
By right-clicking on the line and selecting "Toggle Breakpoint".
By using the keyboard shortcut CTRL+G.

The currently executed line in the script is highlighted in yellow, making it easy to follow the flow.

During debugging, several stepping options are available:

Step Into: Executes the next line and enters an included script, if present. Debugging continues in the included script.
Step: Executes the next line, including any included scripts, but does not enter the debugger for those scripts. The debugger moves to the next line in the main script.

Additionally, the following commands are available:

Continue: Resumes normal script execution until the next breakpoint or the end of the script.
Interrupt: Pauses execution and stops at the next line to be executed. Useful for long-running scripts or infinite loops.
Stop: Immediately terminates the script execution.

By right-clicking on a line and selecting "Set Next Statement", you can directly set the next line to be executed. This can also be a line earlier than the currently executed one.

The debugger dialog provides a convenient way to monitor variables.

Variables can be added or viewed as follows:

Previously defined variables can be selected from the list at the bottom.
New variables can be entered manually using the notation &V[VariableName].
By right-clicking on a line containing a variable, you can add it directly via the context menu.

The value of each variable is displayed in the list. For long text variables, you can download the content by clicking the button with three dots, which is particularly useful for large data sets.

Breakpoints for Variables:

If the "Break" checkbox next to a variable is activated, the debugger will pause whenever the value of that variable changes.
Variables with changed values are highlighted in red for better visibility.

Filter Option:

The list of variables can be filtered. Activate the "Filter" checkbox and enter part of the variable name to narrow down the list.

Introduction to the Debugger	The GuiXT Script Editor Pro debugger is a powerful tool that allows you to step through InputScripts. It enables you to set breakpoints to pause the script execution at specific points and analyze its current state. The debugger allows you to monitor variables in real time, verify their values, and track changes. It is specifically designed to efficiently identify and fix issues or errors in InputScripts. Note: The debugger works exclusively with InputScripts, as they represent the logical programming layer in GuiXT. Standard GuiXT scripts that only modify the layout cannot be debugged. Key features include: Step-by-step execution: Execute the script line by line to analyze its flow. Setting breakpoints: Pause execution at predefined points. Variable inspector: View and monitor variable values during debugging. The debugger provides an ideal foundation for analyzing complex InputScripts and optimizing their functionality.
Activating the Debugger	If GuiXT is running and an appropriate SAP screen is open, the debugger can be activated by pressing the "Debug" button. This opens a dialog for monitoring variables. Once an InputScript is started on the SAP screen, debugging is automatically activated. You can step through the script to analyze its execution. Additionally, you can set breakpoints to pause at specific points and review the current state. You can also jump to any line in the script.
Breakpoints	Breakpoints can be set or removed in several ways: By clicking on the area to the left of the line number. By right-clicking on the line and selecting "Toggle Breakpoint". By using the keyboard shortcut CTRL+G. The currently executed line in the script is highlighted in yellow, making it easy to follow the flow.
Step-by-Step Execution (Stepping)	During debugging, several stepping options are available: Step Into: Executes the next line and enters an included script, if present. Debugging continues in the included script. Step: Executes the next line, including any included scripts, but does not enter the debugger for those scripts. The debugger moves to the next line in the main script. Additionally, the following commands are available: Continue: Resumes normal script execution until the next breakpoint or the end of the script. Interrupt: Pauses execution and stops at the next line to be executed. Useful for long-running scripts or infinite loops. Stop: Immediately terminates the script execution. By right-clicking on a line and selecting "Set Next Statement", you can directly set the next line to be executed. This can also be a line earlier than the currently executed one.
Variable Inspector	The debugger dialog provides a convenient way to monitor variables. Variables can be added or viewed as follows: Previously defined variables can be selected from the list at the bottom. New variables can be entered manually using the notation &V[VariableName]. By right-clicking on a line containing a variable, you can add it directly via the context menu. The value of each variable is displayed in the list. For long text variables, you can download the content by clicking the button with three dots, which is particularly useful for large data sets. Breakpoints for Variables: If the "Break" checkbox next to a variable is activated, the debugger will pause whenever the value of that variable changes. Variables with changed values are highlighted in red for better visibility. Filter Option: The list of variables can be filtered. Activate the "Filter" checkbox and enter part of the variable name to narrow down the list.