Event Break Conditions
An event break condition causes the application to pass control to the Debugger at the beginning of the associated event block. You set event break conditions on the Breakpoints: Events, Errors and Threads portlet (Other portlet tab) of the Debug tab.
You can set event break conditions for the following events:
All Events
Set this condition to turn on all of the event's break conditions at once.
Recognized User Events
Set this condition for a defined OpenROAD user event.
OpenROAD activates the Debugger just before any user event block executes.
Unrecognized User Events
Set this condition for a user event that is not defined for OpenROAD.
OpenROAD passes control to the Debugger when a frame receives a user event for which it has no user event block or for which it is not explicitly waiting (that is, there is no WaitFor method waiting for that user event).
The Unrecognized User Event helps catch common programming errors that result from a frame's receiving a user event for which it has no corresponding event block. The frame does not recognize the event and ignores it. This situation can occur because the event block is missing or the user event name is misspelled, either in the event block or in the SendUserEvent statement.
DB Events
Set this condition for database events.
The application passes control to the Debugger just before any database event block executes.
Window Manager Events
Set this condition for any event that is not a user or database event. Entry events, for example, are window manager events.
The application gives control to the Debugger just before the execution of any event block defined for a window manager event, that is, all event blocks except those for user or database events.
If a particular window event has no defined event blocks in the application, that event, if it occurs, does not cause a break in the application.