Break on Event Dialog
When the Debugger encounters an event break condition that you set, OpenROAD stops the application execution and turns control over to the Debugger, which displays the Break on Event dialog containing the name of the event. The ability to edit user and database events is helpful when you are debugging because you can manipulate the event before it is executed.
Depending on the type of event that was intercepted, the format of this dialog and the options for further debugging will vary. If the event named is a user or a database event, you can edit the event and then click a button on the dialog to control the next step in the event break execution.
For a break on a user event, you can also edit the event's name and three of its message parameters (messageinteger, messagevarchar, and messagefloat). For a database event, you can edit the name or text of the event. For window manager events, you can only use the buttons to process the event.
If the event that caused the break is part of an event chain, the message at the top of the dialog does not necessarily name the actual event in the chain that caused the break. To see this name, click the Break button.
The buttons on the Break on Event dialog provide the following options:
Break
Continues the event break execution.
It displays the Debugger window positioned on the first statement in the event block for the event that caused the break. From here, you can perform all of the Debugger functions available from the Debugger window. For more information about the Debugger window, see How You Can Debug Applications.
In the case of chained events, the block on which the Debugger window is positioned may not be the block that is named in the message on the Event Break Conditions dialog.
Ignore
Skips the event named in the dialog.
If you select this option, execution continues as if the event did not occur.
Continue
Executes the event.
The application does not stop until the next break condition is encountered.