Working with the GISDK Debugger

GISDK includes a debugger that helps you find and fix runtime problems in your GISDK macros. You can set breakpoints in resource files, see the call stack, see the values of variables, and set up a watch list. The look and feel of this debugger is very similar to other debuggers, such as the one for Microsoft Visual Studio.

The GISDK Debugger runs along side Maptitude, in a separate window. You start the GISDK Debugger from the GISDK toolbox. You can set breakpoints at lines in the resource files that have been compiled into a UI Database. When you run macros in that UI Database and reach a breakpoint, focus shifts to the GISDK Debugger window, where you have considerable control over subsequent execution. For example, you can:

• Step through line by line in the resource file
• Execute up to a line
• Return to the calling macro
• Move the point of execution to a different line
• Change values of variables and sub-elements of arrays and compound variables
• Continue normal execution

Also, if the GISDK Debugger is not running and Maptitude encounters an error in your UI Database, you can choose to open the GISDK Debugger and go right to the source of the error.

For more information, see...

Setting Up the GISDK Debugger

Managing the GISDK Debugger Windows

Using the GISDK Debugger

Viewing Errors in the GISDK Debugger