XMappingEvent man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]

XMapEvent(3X11)						       XMapEvent(3X11)

NAME
       XMapEvent, XMappingEvent - MapNotify and MappingNotify event structures

DESCRIPTION
       The structure for MapNotify events contains:

       typedef struct {
	       int type;	       /* MapNotify */
	       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 event;
	       Window window;
	       Bool  override_redirect;	 /*  boolean,  is override set... */ }
       XMapEvent;

       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 application, it sends an XGraphicsExposeEvent	struc‐
       ture  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  event member is set either to the window that was mapped or to its
       parent, depending on whether StructureNotify or SubstructureNotify  was
       selected.  The  window member is set to the window that was mapped. The
       override_redirect member is set to the override-redirect	 attribute  of
       the  window.  Window manager clients normally should ignore this window
       if the override-redirect attribute is True, because these  events  usu‐
       ally are generated from pop-ups, which override structure control.

       The structure for MappingNotify events is:

       typedef struct {
	       int type;	       /* MappingNotify */
	       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;	       /* unused */
	       int request;	       /* one of MappingModifier,
					  MappingKeyboard, MappingPointer */
	       int first_keycode;      /* first keycode */
	       int count;	       /* defines range of change
					  w. first_keycode */ } XMappingEvent;

       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 application, it sends an XGraphicsExposeEvent struc‐
       ture 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 request member is set to indicate the kind of mapping  change  that
       occurred	 and  can be MappingModifier, MappingKeyboard, MappingPointer.
       If it is MappingModifier, the modifier mapping was changed.  If	it  is
       MappingKeyboard,	 the  keyboard	mapping was changed. If it is Mapping‐
       Pointer, the pointer button mapping was changed. The first_keycode  and
       count members are set only if the request member was set to MappingKey‐
       board. The number in first_keycode represents the first number  in  the
       range  of  the altered mapping, and count represents the number of key‐
       codes altered.

SEE ALSO
       XAnyEvent(3X11), XButtonEvent(3X11), XCreateWindowEvent(3X11),  XCircu‐
       lateEvent(3X11),	  XCirculateRequestEvent(3X11),	 XColormapEvent(3X11),
       XConfigureEvent(3X11),			 XConfigureRequestEvent(3X11),
       XCrossingEvent(3X11),   XDestroyWindowEvent(3X11),   XErrorEvent(3X11),
       XExposeEvent(3X11),	  XFocusChangeEvent(3X11),	  XGraphicsEx‐
       poseEvent(3X11),	  XGravityEvent(3X11),	 XKeymapEvent(3X11),   XMapRe‐
       questEvent(3X11), XPropertyEvent(3X11),	XReparentEvent(3X11),  XResiz‐
       eRequestEvent(3X11), XSelectionClearEvent(3X11), XSelectionEvent(3X11),
       XSelectionRequestEvent(3X11), XUnmapEvent(3X11), XVisibilityEvent(3X11)

       Xlib -- C Language X Interface

							       XMapEvent(3X11)
[top]

List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net