XMappingEvent(3)

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

NAME

6       XMapEvent, XMappingEvent - MapNotify and MappingNotify event structures
7

STRUCTURES

9       The structure for MapNotify events contains:
10
11       typedef struct {
12               int type;       /* MapNotify */
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 event;
17               Window window;
18               Bool override_redirect; /* boolean, is override set... */
19       } XMapEvent;
20
21       When you receive this event, the structure members are set as follows.
22
23       The type member is set to the event type constant name that uniquely
24       identifies it.  For example, when the X server reports a GraphicsExpose
25       event to a client application, it sends an XGraphicsExposeEvent struc‐
26       ture with the type member set to GraphicsExpose.  The display member is
27       set to a pointer to the display the event was read on.  The send_event
28       member is set to True if the event came from a SendEvent protocol
29       request.  The serial member is set from the serial number reported in
30       the protocol but expanded from the 16-bit least-significant bits to a
31       full 32-bit value.  The window member is set to the window that is most
32       useful to toolkit dispatchers.
33
34       The event member is set either to the window that was mapped or to its
35       parent, depending on whether StructureNotify or SubstructureNotify was
36       selected.  The window member is set to the window that was mapped.  The
37       override_redirect member is set to the override-redirect attribute of
38       the window.  Window manager clients normally should ignore this window
39       if the override-redirect attribute is True, because these events usu‐
40       ally are generated from pop-ups, which override structure control.
41
42       The structure for MappingNotify events is:
43
44       typedef struct {
45               int type;       /* MappingNotify */
46               unsigned long serial;   /* # of last request processed by server */
47               Bool send_event;        /* true if this came from a SendEvent request */
48               Display *display;       /* Display the event was read from */
49               Window window;  /* unused */
50               int request;    /* one of MappingModifier, MappingKeyboard,
51                          MappingPointer */
52               int first_keycode;      /* first keycode */
53               int count;      /* defines range of change w. first_keycode*/
54       } XMappingEvent;
55
56       When you receive this event, the structure members are set as follows.
57
58       The type member is set to the event type constant name that uniquely
59       identifies it.  For example, when the X server reports a GraphicsExpose
60       event to a client application, it sends an XGraphicsExposeEvent struc‐
61       ture with the type member set to GraphicsExpose.  The display member is
62       set to a pointer to the display the event was read on.  The send_event
63       member is set to True if the event came from a SendEvent protocol
64       request.  The serial member is set from the serial number reported in
65       the protocol but expanded from the 16-bit least-significant bits to a
66       full 32-bit value.  The window member is set to the window that is most
67       useful to toolkit dispatchers.
68
69       The request member is set to indicate the kind of mapping change that
70       occurred and can be MappingModifier, MappingKeyboard, MappingPointer.
71       If it is MappingModifier, the modifier mapping was changed.  If it is
72       MappingKeyboard, the keyboard mapping was changed.  If it is Mapping‐
73       Pointer, the pointer button mapping was changed.  The first_keycode and
74       count members are set only if the request member was set to MappingKey‐
75       board.  The number in first_keycode represents the first number in the
76       range of the altered mapping, and count represents the number of key‐
77       codes altered.
78

NAME

STRUCTURES

SEE ALSO