Introduced in the 1995 ANSI M[UMPS] Windowing Application Programmer's Interface standard.
This command causes an event to occur. For examples, see the
structured system variable ^$WINDOW. Depending on the type
of event thst is to occur, the event specification will be
in:
^$WINDOW (window,"EVENT",type)
^$WINDOW(window,"G",gadget,"EVENT",type)
^$WINDOW(window,"T",timer,"EVENT",type)
^$WINDOW(window,"M",menu,"CHOICE",item,"EVENT",type)
The ability to trigger events that are to be processed by other processes is introduced.
Suppose that the value of local variable X is the process-ID of one process, and that this process is intended to process events that are triggered by another job. Let the value of local variable Y be the process-ID of this other job.
Either process could issue a command like:
SET ^$JOB(X,"EVENT","IPC",Y)="^PROGRAM"
When the process identified by Y issues the command
ETRIGGER "^$JOB(X,""EVENT"",""IPC"",Y)"
the process identified by X will start executing the
routine ^PROGRAM. When the process identified by
X started recognition of IPC events with the
command ESTART "IPC", this processing will occur
synchronously, when the recognition was started with
ASTART "IPC", this processing will occur
asynchronously.
This document is © Ed de Moel, 1995-2005.
It is part of a book by Ed de Moel that is published under
the title "M[UMPS] by Example" (ISBN 0-918118-42-5).
Printed copies of the book are no longer available.
This document describes the various commands that are defined in the M[UMPS] language standard (ANSI X11.1, ISO 11756).
The information in this document is NOT authoritative
and subject to be modified at any moment.
Please consult the appropriate (draft) language standard for an
authoritative definition.
In this document, information is included that will
appear in
future standards.
The MDC cannot guarantee that these 'next'
standards will indeed appear.