☜	MWAPI - ETRIGGER Draft MDC Standard					☞

9.4.3 ETRIGGER

ETR [ IGGER ] postcond SP especref [ : einforef ]

The M[UMPS] command ETRIGGER causes an event to occur. If this event is enabled, call back processing for it will occur subsequently.

The event occurs for the window, element, or menu choice specified by the especref. If the window, element, or menu choice specified by the especref does not exist, an error condition occurs with an ecode = "M48" and $EREF containing a value that indicates the non-existent window, element, or menu choice.

The event that occurs is specified by the etype component of the especref. If the especref does not contain a valid etype, an error condition occurs with an ecode = "M47".

No additional events occur as consequence of an event that occurs as a result of execution of an ETRIGGER command. For example, executing an ETRIGGER command that causes a focus event to occur does not automatically cause an unfocus or change event to occur.

When call back processing occurs for the event, the following einfoattribute nodes are provided automatically in ^$EVENT:

• For all events, CLASS, SEQUENCE, TYPE and WINDOW.
• When an event occurs for an element, ELEMENT.
• When an event occurs for a menu choice, CHOICE and ELEMENT.
• For change and unfocus events, OK.

Other einfoattribute nodes can be provided by the application via the einforef argument. If einforef is present, then for each immediately descendant subscript of einforef which matches an einfoattribute that (a) is defined for the event type specified in the especref and (b) is not provided automatically in ^$EVENT, as described above, the value of the ^$EVENT einfoattribute is set to the value of the corresponding einforef node.

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 30-Nov-2011, 20:11:12.

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