|
NAMExcb_input_get_device_property -SYNOPSIS#include <xcb/xinput.h>Request functionxcb_input_get_device_property_cookie_t xcb_input_get_device_property(xcb_connection_t *conn, xcb_atom_t property, xcb_atom_t type, uint32_t offset, uint32_t len, uint8_t device_id, uint8_t _delete); Reply datastructuretypedef struct xcb_input_get_device_property_reply_t { uint8_t response_type; uint8_t xi_reply_type; uint16_t sequence; uint32_t length; xcb_atom_t type; uint32_t bytes_after; uint32_t num_items; uint8_t format; uint8_t device_id; uint8_t pad0[10]; } xcb_input_get_device_property_reply_t; Reply functionxcb_input_get_device_property_reply_t *xcb_input_get_device_property_reply(xcb_connection_t *conn, xcb_input_get_device_property_cookie_t cookie, xcb_generic_error_t **e); Reply accessorsxcb_input_get_device_property_items_t *xcb_input_get_device_property_items (const xcb_input_get_device_property_request_t *reply)REQUEST ARGUMENTS
REPLY FIELDS
DESCRIPTIONRETURN VALUEReturns an xcb_input_get_device_property_cookie_t. Errors have to be handled when calling the reply function xcb_input_get_device_property_reply.If you want to handle errors in the event loop instead, use xcb_input_get_device_property_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. |