DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH
 
X Version 11 (Release 5)

XSendEvent(XS)


XSendEvent -- send events and pointer motion history structure

Syntax

   Status XSendEvent(display, w, propagate, event_mask, event_send)
         Display *display;
         Window w;
         Bool propagate;
         long event_mask;
         XEvent *event_send;
   

unsigned long XDisplayMotionBufferSize(display) Display *display;

XTimeCoord *XGetMotionEvents(display, w, start, stop, nevents_return) Display *display; Window w; Time start, stop; int *nevents_return;

Arguments


display
Specifies the connection to the X server.

event_mask
Specifies the event mask.

event_send
Specifies the event that is to be sent.

nevents_return
Returns the number of events from the motion history buffer.

propagate
Specifies a Boolean value.

start
stop
Specify the time interval in which the events are returned from the motion history buffer. You can pass a timestamp or CurrentTime.

w
Specifies the window the window the event is to be sent to, PointerWindow, or InputFocus.

Description

The XSendEvent function identifies the destination window, determines which clients should receive the specified events, and ignores any active grabs. This function requires you to pass an event mask. For a discussion of the valid event mask names, see section 10.3 of Xlib - C Language X Interface. This function uses the w argument to identify the destination window as follows: To determine which clients should receive the specified events, XSendEvent uses the propagate argument as follows: The event in the XEvent structure must be one of the core events or one of the events defined by an extension (or a ``BadValue'' error results) so that the X server can correctly byte-swap the contents as necessary. The contents of the event are otherwise unaltered and unchecked by the X server except to force send_event to True in the forwarded event and to set the serial number in the event correctly.

XSendEvent returns zero if the conversion to wire protocol format failed and returns nonzero otherwise. XSendEvent can generate ``BadValue'' and ``BadWindow'' errors.

The server may retain the recent history of the pointer motion and do so to a finer granularity than is reported by MotionNotify events. The XGetMotionEvents function makes this history available.

The XGetMotionEvents function returns all events in the motion history buffer that fall between the specified start and stop times, inclusive, and that have coordinates that lie within the specified window (including its borders) at its present placement. If the server does not support motion history, or if the start time is later than the stop time, or if the start time is in the future, no events are returned, and XGetMotionEvents returns NULL. If the stop time is in the future, it is equivalent to specifying CurrentTime. XGetMotionEvents can generate a ``BadWindow'' error.

Structures

The XTimeCoord structure contains:
   typedef struct {
         Time time;
         short x, y;
   } XTimeCoord;
The time member is set to the time, in milliseconds. The x and y members are set to the coordinates of the pointer and are reported relative to the origin of the specified window.

Diagnostics


``BadValue''
Some numeric value falls outside the range of values accepted by the request. Unless a specific range is specified for an argument, the full range defined by the argument's type is accepted. Any argument defined as a set of alternatives can generate this error.

``BadWindow''
A value for a Window argument does not name a defined Window.

See also

XAnyEvent(XS), XIfEvent(XS), XNextEvent(XS), XPutBackEvent(XS)

Xlib - C Language X Interface
© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003