|
NAMExcb_input_open_device -SYNOPSIS#include <xcb/xinput.h>Request functionxcb_input_open_device_cookie_t xcb_input_open_device(xcb_connection_t *conn, uint8_t device_id); Reply datastructuretypedef struct xcb_input_open_device_reply_t { uint8_t response_type; uint8_t xi_reply_type; uint16_t sequence; uint32_t length; uint8_t num_classes; uint8_t pad0[23]; } xcb_input_open_device_reply_t; Reply functionxcb_input_open_device_reply_t *xcb_input_open_device_reply(xcb_connection_t *conn, xcb_input_open_device_cookie_t cookie, xcb_generic_error_t **e); Reply accessorsxcb_input_input_class_info_t *xcb_input_open_device_class_info(const xcb_input_open_device_request_t *reply); int xcb_input_open_device_class_info_length(const xcb_input_open_device_reply_t *reply); xcb_input_input_class_info_iterator_t
xcb_input_open_device_class_info_iterator(const
xcb_input_open_device_reply_t *reply); uint8_t
*xcb_input_open_device_pad_1 (const xcb_input_open_device_request_t *reply)
REQUEST ARGUMENTS
REPLY FIELDS
DESCRIPTIONRETURN VALUEReturns an xcb_input_open_device_cookie_t. Errors have to be handled when calling the reply function xcb_input_open_device_reply.If you want to handle errors in the event loop instead, use xcb_input_open_device_unchecked. See xcb-requests(3) for details. ERRORSThis request does never generate any errors.SEE ALSOAUTHORGenerated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
Visit the GSP FreeBSD Man Page Interface. |