Programming Guide - Actian

How You Can Use Break ConditionsSet Event Break ConditionsBreak on Event DialogWindow Manager EventsSet this condition for any event that is not a user or database event. Entryevents, for example, are window manager events.The application gives control to the Debugger just before the execution ofany event block defined for a window manager event, that is, all eventblocks 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.You can set event break conditions on the Breakpoints: Events, Errors andThreads portlet (Other portlet tab) of the Debug tab.To set event break conditions1. Click the Develop tab and select the application in which you want to setevent break conditions in the Applications portlet.2. Click the Debug tab.3. Click the Other portlet tab on the right side of the Workbench window.The Breakpoints: Events, Errors and Threads portlet is displayed.4. In the Event Break Conditions section, select one or more types of eventsthat you want to set as break conditions, or check All Events to set breakconditions for all events.Event break conditions are displayed in the Activations portlet of the Debugtab.If you want to deactivate or reactivate a break condition, clear or select theappropriate check box in the Activations portlet.When the Debugger encounters an event break condition that you set,OpenROAD stops the application execution and turns control over to theDebugger, which displays the Break on Event dialog containing the name ofthe event. The ability to edit user and database events is helpful when you aredebugging because you can manipulate the event before it is executed.Depending on the type of event that was intercepted, the format of this dialogand the options for further debugging will vary. If the event named is a user ora database event, you can edit the event and then click a button on the dialogto control the next step in the event break execution.Debugging Your Application 451