|
NAMExcb_get_motion_events -SYNOPSIS#include <xcb/xproto.h>Request functionxcb_get_motion_events_cookie_t xcb_get_motion_events(xcb_connection_t *conn, xcb_window_t window, xcb_timestamp_t start, xcb_timestamp_t stop); Reply datastructuretypedef struct xcb_get_motion_events_reply_t { uint8_t response_type; uint8_t pad0; uint16_t sequence; uint32_t length; uint32_t events_len; uint8_t pad1[20]; } xcb_get_motion_events_reply_t; Reply functionxcb_get_motion_events_reply_t *xcb_get_motion_events_reply(xcb_connection_t *conn, xcb_get_motion_events_cookie_t cookie, xcb_generic_error_t **e); Reply accessorsxcb_timecoord_t *xcb_get_motion_events_events(const xcb_get_motion_events_request_t *reply); int xcb_get_motion_events_events_length(const xcb_get_motion_events_reply_t *reply); xcb_timecoord_iterator_t
xcb_get_motion_events_events_iterator(const
xcb_get_motion_events_reply_t *reply);
REQUEST ARGUMENTS
REPLY FIELDS
DESCRIPTIONRETURN VALUEReturns an xcb_get_motion_events_cookie_t. Errors have to be handled when calling the reply function xcb_get_motion_events_reply.If you want to handle errors in the event loop instead, use xcb_get_motion_events_unchecked. See xcb-requests(3) for details. ERRORSThis request does never generate any errors.SEE ALSOAUTHORGenerated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
Visit the GSP FreeBSD Man Page Interface. |