Code Editor Breakpoints

Navigation:  Macros > Testing Macros > Testing the Logic >

Code Editor Breakpoints

Previous pageReturn to chapter overviewNext page

Breakpoints are useful when stepping through your code, to move quickly to the line that interest you, using the F9 key and then switch to the F7 or F8 mode.


To insert a breakpoint in the code editor, click in the left margin, or gutter.



The current line's background will change to red, and a stop sign will appear in the margin.



When stepping through a macro, if you reach a breakpoint, it will be denoted by an arrow in the margin, which allows you to see the breakpoint on which you have stopped.



Note that you can only set breakpoints on lines that contain instructions. You will not be able to set a breakpoint on a full-line comments (nor would there be any use for it). Also, you can only set breakpoints when the macro has been compiled.


Later, when discussing the Macros Debugger, we will see that it has more powerful breakpoints, which can be set to break only for a particular condition (eg. when the n_TokenDate reaches a certain value). The reasons for this disparity are as follows :


Testing in the code editor is meant to test the flow of logic of your code, using some typical expected values (as seen before, the testing capabilities of the code editor are limited due to the functions that cannot be evaluated at design-time).

The need for conditional breakpoints is lessened because you can set the Initial Conditions yourself.

Topic 108252 updated on 07-Mar-2002.
Topic URL: