XClientMessageEvent(3X11) XLIB FUNCTIONSXClientMessageEvent(3X11)


NAME
       XClientMessageEvent - ColormapNotify event structure

STRUCTURES
       The structure for ClientMessage events contains:

       typedef struct {
            int type;                /* ClientMessage */
            unsigned long serial;    /* # of last request processed by server */
            Bool send_event;         /* true if this came from a SendEvent request */
            Display *display;        /* Display the event was read from */
            Window window;
            Atom message_type;
            int format;
            union {
                 char b[20];
                 short s[10];
                 long l[5];
                    } data;
       } XClientMessageEvent;

       When you receive this event, the structure members are set
       as follows.

       The type member is set to the event type constant name
       that uniquely identifies it.  For example, when the X
       server reports a GraphicsExpose event to a client applica-
       tion, it sends an XGraphicsExposeEvent structure with the
       type member set to GraphicsExpose.  The display member is
       set to a pointer to the display the event was read on.
       The send_event member is set to True if the event came
       from a SendEvent protocol request.  The serial member is
       set from the serial number reported in the protocol but
       expanded from the 16-bit least-significant bits to a full
       32-bit value.  The window member is set to the window that
       is most useful to toolkit dispatchers.

       The message_type member is set to an atom that indicates
       how the data should be interpreted by the receiving
       client.  The format member is set to 8, 16, or 32 and
       specifies whether the data should be viewed as a list of
       bytes, shorts, or longs.  The data member is a union that
       contains the members b, s, and l.  The b, s, and l members
       represent data of 20 8-bit values, 10 16-bit values, and 5
       32-bit values.  Particular message types might not make
       use of all these values.  The X server places no interpre-
       tation on the values in the window, message_type, or data
       members.

SEE ALSO
       XAnyEvent(3X11), XButtonEvent(3X11), XCreateWindow-
       Event(3X11), XCirculateEvent(3X11), XCircu-
       lateRequestEvent(3X11), XColormapEvent(3X11), XConfig-
       ureEvent(3X11), XConfigureRequestEvent(3X11),



X Version 11                Release 5                           1

XClientMessageEvent(3X11) XLIB FUNCTIONSXClientMessageEvent(3X11)


       XCrossingEvent(3X11), XDestroyWindowEvent(3X11), XEr-
       rorEvent(3X11), XExposeEvent(3X11), XFo-
       cusChangeEvent(3X11), XGraphicsExposeEvent(3X11), XGravi-
       tyEvent(3X11), XKeymapEvent(3X11), XMapEvent(3X11),
       XMapRequestEvent(3X11), XPropertyEvent(3X11), XRepar-
       entEvent(3X11), XResizeRequestEvent(3X11), XSelection-
       ClearEvent(3X11), XSelectionEvent(3X11), XSelectionRe-
       questEvent(3X11), XUnmapEvent(3X11), XVisibili-
       tyEvent(3X11)
       Xlib - C Language X Interface















































X Version 11                Release 5                           2