Maptitude GISDK Help |
You can set up the GISDK Debugger by opening one or more resource files and setting breakpoints. When you start running the macros in the UI Database into which these resources files have been compiled, execution will halt at the breakpoints. Breakpoints for dialog boxes must be set in a do/endItem section of code, such as the Init macro.
The GISDK Debugger is normally started by clicking
on the GISDK toolbox. You can also start the GISDK Debugger, or open the
debugger window, with StartDebugger().
The Variables window keeps track of all of the variables. If there are certain variables that you want to track, you can add them as items in the Watch window. You can also keep track of the value of any expression in this window.
Breakpoints and watch expressions persist between sessions.
To Set Up the GISDK Debugger
To do this... |
Do this... |
Open a resource file |
Click
|
Set a breakpoint |
Click
on a line in a source code window and click |
Make a breakpoint conditional |
Choose a breakpoint in the Breakpoints window, right-click to display the context menu, and choose Condition. Enter a GISDK expression to control whether execution stops at this breakpoint. |
Find a breakpoint |
Double-click on the breakpoint in the Breakpoints window. The line will be highlighted in the appropriate source code window, which will be brought to the front and scrolled if necessary. |
Remove a breakpoint |
Click
on a line in a source code window that is marked as a breakpoint
and click |
Remove all breakpoints |
Right-click on the Breakpoints window and choose Delete All to display the Delete All dialog box. Click Yes to delete all the breakpoints, or No to keep them all. |
Windows returns to the Maptitude program window.
©2025 Caliper Corporation | www.caliper.com |