Recent News
|
InnPlanner 2010 Released
New faster database engine, more customization features, weekly tariffs, full multi-user work support and much more... | |
InnPlanner 2010 RC1
InnPlanner 2010 Release Candidate 1 is ready for downloading and testing. You can download it from the "Downloads" section. |
|
|
Hotel Software Documentation
Script Debugging
Introduction
Script debugging is a powerful tool which may help you in understanding script work and finding errors if something works wrong.
To get access to debugging menu, run the script editor from the main menu: Designer->Edit Database Scripts.
The debugging option will be disabled, if the script editor is opened from another place.
Description
Debug menu contains the following options:
- Start - run the script
- Start Debug - execute the script, but stop before the first command. This option allows watching the script work step by step.
- Toggle Breakpoint - create or delete a breakpoint for the selected script line. While executing the script, but before running a line with the breakpoint, the program shall stop, so you have the ability to check variable values or change the script execution order.
- Stop on BreakPoints - if the flag is not checked, there will be no stops at breakpoints while script execution. It is convenient to uncheck this flag if you want to see the script work in normal mode, but you don't want to delete the created breakpoints.
Script debugging
When the script execution is stopped at a Breakpoint, or it has been executed via Start Debug option, a debagging window shall show up on the screen:
This window is similar to script editor, but is used for analysis of a script work. The command, before which the script has been stopped, is shown in red. Note, that this command has not yet been executed.
In the left part of the window a list of local and global variables, used in the script, is shown, together with their values.
At the top of the window there is a debugging control panel:
- Continue - to continue script execution starting with the current command.
- Next Line - execute the current command and stop the script for debugging. This button is useful, when you need to check how the command affects variable changes.
- Skip Line - skip the current line and go to a next one.
- Skip Sub - end the current cycle or the activated user function.
- Stop - stop script execution, return to the script editor.
Be careful using "Skip Line/Sub" command in debugging. Skipping a part of the script will affect its functionality.
See Also:
Scripting Basics
Script Designer
Using Variables
User Functions
Action Editor
List of actions
|
|
|
|
Today"s Poll
What software do use for your inn/b&b/hotel/etc?
|
About