Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   3690 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

XClientMessageEvent(3X11)	     X11R5	     XClientMessageEvent(3X11)

NAME
       XClientMessageEvent - ColormapNotify event structure

STRUCTURES
       The structure for 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 event to a
       client application, it sends an structure with the type member set to
       The display member is set to a pointer to the display the event was
       read on.	 The send_event member is set to if the event came from a pro‐
       tocol 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.	Par‐
       ticular message types might not make use of all these values.  The X
       server places no interpretation on the values in the window, mes‐
       sage_type, or data members.

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),
       XMapEvent(3X11), XMapRequestEvent(3X11), XPropertyEvent(3X11), XRepar‐
       entEvent(3X11), XResizeRequestEvent(3X11), XSelectionClearEvent(3X11),
       XSelectionEvent(3X11), XSelectionRequestEvent(3X11), XUnmapEvent(3X11),
       XVisibilityEvent(3X11)
       Xlib - C Language X Interface

						     XClientMessageEvent(3X11)

Vote for polarhome