Programming Guide - Actian

Event-based ProgrammingField EventsBecause users mostly interact with individual fields on a form, the events forfields are the most diverse and complex. For example, the following tablesummarizes the events that a user can trigger for a button field:EventClickDoubleClickClickPointDetailsDragBoxDragSegmentMovedPropertiesResizedSelectUnSelectHow Triggered by UserUser clicks the field with the Select mouse button when thefield has a bias of FB_LANDABLE or FB_CHANGEABLE.User double-clicks the field with the Select mouse button.This event is not available for fields with biases ofFB_VISIBLE, FB_DIMMED, and FB_INVISIBLE.User clicks a field that has a bias of FB_CLICKPOINT.User clicks the field with the Details button. This event isnot available for fields with biases of FB_VISIBLE,FB_DIMMED, and FB_INVISIBLE.User draws a drag box in a field that has a bias ofFB_DRAGBOX.User draws a drag segment in a field that has a bias ofFB_DRAGSEGMENT.User moves a field with a bias of FB_MOVEABLE orFB_FLEXIBLE.User clicks a field with the Properties button. This event isnot available for fields with biases of FB_VISIBLE,FB_DIMMED, and FB_INVISIBLE.User resizes a field that has a bias of FB_RESIZEABLE orFB_FLEXIBLE.User selects a field that has a bias of FB_FLEXIBLE,FB_RESIZABLE, FB_MOVEABLE, or FB_MARKABLE.User deselects a field that has a bias of FB_FLEXIBLE,FB_RESIZABLE, FB_MOVEABLE, or FB_MARKABLE.For a complete list of the events for each of the OpenROAD fields, see theLanguage Reference Guide online help.Many events are triggered only when a field is set to a certain bias, allowingyou to provide code that is executed only when the user is actually performinga certain task. For example, the Click event can be triggered only when theuser is actually allowed to click the button, as determined by the allowablebiases. For more information about field biases, see the User Guide.Managing Event Queues 323