1XClientMessageEvent(3)          XLIB FUNCTIONS          XClientMessageEvent(3)
2
3
4

NAME

6       XClientMessageEvent - ClientMessage event structure
7

STRUCTURES

9       The structure for ClientMessage events contains:
10
11       typedef struct {
12            int type;                /* ClientMessage */
13            unsigned long serial;    /* # of last request processed by server */
14            Bool send_event;         /* true if this came from a SendEvent request */
15            Display *display;        /* Display the event was read from */
16            Window window;
17            Atom message_type;
18            int format;
19            union {
20                 char b[20];
21                 short s[10];
22                 long l[5];
23                    } data;
24       } XClientMessageEvent;
25
26       When you receive this event, the structure members are set as follows.
27
28       The type member is set to the event type constant name that uniquely
29       identifies it.  For example, when the X server reports a GraphicsExpose
30       event to a client application, it sends an XGraphicsExposeEvent struc‐
31       ture with the type member set to GraphicsExpose.  The display member is
32       set to a pointer to the display the event was read on.  The send_event
33       member is set to True if the event came from a SendEvent protocol
34       request.  The serial member is set from the serial number reported in
35       the protocol but expanded from the 16-bit least-significant bits to a
36       full 32-bit value.  The window member is set to the window that is most
37       useful to toolkit dispatchers.
38
39       The message_type member is set to an atom that indicates how the data
40       should be interpreted by the receiving client.  The format member is
41       set to 8, 16, or 32 and specifies whether the data should be viewed as
42       a list of bytes, shorts, or longs.  The data member is a union that
43       contains the members b, s, and l.  The b, s, and l members represent
44       data of twenty 8-bit values, ten 16-bit values, and five 32-bit values.
45       Particular message types might not make use of all these values.  The X
46       server places no interpretation on the values in the window, mes‐
47       sage_type, or data members.
48

SEE ALSO

50       XAnyEvent(3), XButtonEvent(3), XCreateWindowEvent(3), XCircula‐
51       teEvent(3), XCirculateRequestEvent(3), XColormapEvent(3), XConfig‐
52       ureEvent(3), XConfigureRequestEvent(3), XCrossingEvent(3), XDestroyWin‐
53       dowEvent(3), XErrorEvent(3), XExposeEvent(3), XFocusChangeEvent(3),
54       XGraphicsExposeEvent(3), XGravityEvent(3), XKeymapEvent(3),
55       XMapEvent(3), XMapRequestEvent(3), XPropertyEvent(3), XRepar‐
56       entEvent(3), XResizeRequestEvent(3), XSelectionClearEvent(3), XSelec‐
57       tionEvent(3), XSelectionRequestEvent(3), XUnmapEvent(3), XVisibili‐
58       tyEvent(3)
59       Xlib - C Language X Interface
60
61
62
63X Version 11                     libX11 1.3.4           XClientMessageEvent(3)
Impressum