☜	MWAPI - Processing Events Draft MDC Standard					☞

9.3 Processing Events

If event processing is activated, then for each enabled event of type E that occurs, call back processing occurs by execution of an implicit DO command of the form

DO @doargument

where doargument is the value of the EVENT wattribute, elattribute, or cattribute for a window, element, or choice, respectively for etype equal to E, or for a build mode window where doargument is the value of the BEVENT wattribute for betype equal to E..

For each ESTART command, call back processing is carried out for events in the order of their occurrence. If an enabled event occurs while call back processing is not activated, call back processing for it may be deferred until call back processing is activated. While there is no explicit limit on the number of deferred events, deferred events may be lost if not processed quickly.

Call back processing does not occur as a result of modification of ^$DISPLAY or ^$WINDOW by the application.

For close, data key up, and data key down events, if the event is enabled, the normal actions of the underlying windowing platform for that event are inhibited; if the event is not enabled, the normal actions of the underlying windowing platform for that event occur. For other events, the normal actions of the underlying windowing platform occur for the event, whether or not the event is enabled.

Copyright © Standard Documents; 1977-2024 MUMPS Development Committee;
Copyright © Examples: 1995-2024 Ed de Moel;
Copyright © Annotations: 2003-2008 Jacquard Systems Research
Copyright © Annotations: 2008-2024 Ed de Moel.

Some specifications are "approved for inclusion in a future standard". Note that the MUMPS Development Committee cannot guarantee that such future standards will indeed be published.

This page most recently updated on 28-Nov-2011, 21:33:07.

For comments, contact Ed de Moel (demoel@jacquardsystems.com)