ultrix man page for xclientmessageevent

Query: xclientmessageevent

OS: ultrix

Section: 3x11

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

XClientMessageEvent(3X11)					     MIT X11R4						 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 came from a SendEvent
					request */
	    Display *display;	  /* Display 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 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 win-
       dow 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 message_type or
       data members.

See Also
       XAnyEvent(3X11), XButtonEvent(3X11), XCreateWindowEvent(3X11), XCirculateEvent(3X11), XCirculateRequestEvent(3X11), XColormapEvent(3X11),
       XConfigureEvent(3X11), XConfigureRequestEvent(3X11), XCrossingEvent(3X11), XDestroyWindowEvent(3X11), XErrorEvent(3X11), XEx-
       poseEvent(3X11), XFocusChangeEvent(3X11), XGraphicsExposeEvent(3X11), XGravityEvent(3X11), XKeymapEvent(3X11), XMapEvent(3X11), XMapRe-
       questEvent(3X11), XPropertyEvent(3X11), XReparentEvent(3X11), XResizeRequestEvent(3X11), XSelectionClearEvent(3X11), XSelectionEvent(3X11),
       XSelectionRequestEvent(3X11), XUnmapEvent(3X11), XVisibilityEvent(3X11)
       X Window System: The Complete Reference, Second Edition, Robert W. Scheifler and James Gettys

															 XClientMessageEvent(3X11)
Related Man Pages
xclientmessageevent(3x11) - redhat
xresizerequestevent(3x11) - redhat
xclientmessageevent(3x11) - xfree86
xclientmessageevent(3) - x11r4
xmaprequestevent(3x11) - ultrix
Similar Topics in the Unix Linux Community
A short history of UNIX by l.madden@ic.ac.uk
Can I change my hostname without messing things up?
PHP Write Man Pages to MySQL DB
Denial Of Service Attack Update