Breakpoints and debugging: Difference between revisions
(Importing text file) |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Breakpoints are routine operations which cause the model to pause and display a dialog within the execution of a routine. | |||
A system attribute "Break Point Master Control" can be read and set to enable/disable the display of breakpoints. This provides control of any breakpoint(s) in the model. This works in addition to modeller defined breakpoint control attributes, enabling breakpoints to be enabled under complex conditions or at certain stages in a long loop. | |||
In addition, the editor can disable subsequent breakpoints in the same thread using a checkbox in the breakpoint dialog. They are automatically re-enabled upon "continue" of the run. | |||
The Breakpoint dialog has a "Debug" button enabling debugging options to be changed (eg: trace animation) while still at the breakpoint/current<br /> point in the thread. | |||
---- | |||
<font size="2">idkbase note 13</font> | |||
[[Category:Debugging]] | [[Category:Debugging]] | ||
Latest revision as of 12:42, 12 January 2008
Breakpoints are routine operations which cause the model to pause and display a dialog within the execution of a routine.
A system attribute "Break Point Master Control" can be read and set to enable/disable the display of breakpoints. This provides control of any breakpoint(s) in the model. This works in addition to modeller defined breakpoint control attributes, enabling breakpoints to be enabled under complex conditions or at certain stages in a long loop.
In addition, the editor can disable subsequent breakpoints in the same thread using a checkbox in the breakpoint dialog. They are automatically re-enabled upon "continue" of the run.
The Breakpoint dialog has a "Debug" button enabling debugging options to be changed (eg: trace animation) while still at the breakpoint/current
point in the thread.
idkbase note 13