|
NAMExcb_input_get_device_modifier_mapping -SYNOPSIS#include <xcb/xinput.h>Request functionxcb_input_get_device_modifier_mapping_cookie_t xcb_input_get_device_modifier_mapping(xcb_connection_t *conn, uint8_t device_id); Reply datastructuretypedef struct xcb_input_get_device_modifier_mapping_reply_t { uint8_t response_type; uint8_t xi_reply_type; uint16_t sequence; uint32_t length; uint8_t keycodes_per_modifier; uint8_t pad0[23]; } xcb_input_get_device_modifier_mapping_reply_t; Reply functionxcb_input_get_device_modifier_mapping_reply_t *xcb_input_get_device_modifier_mapping_reply(xcb_connection_t *conn, xcb_input_get_device_modifier_mapping_cookie_t cookie, xcb_generic_error_t **e); Reply accessorsuint8_t *xcb_input_get_device_modifier_mapping_keymaps(const xcb_input_get_device_modifier_mapping_request_t *reply); int xcb_input_get_device_modifier_mapping_keymaps_length(const xcb_input_get_device_modifier_mapping_reply_t *reply); xcb_generic_iterator_t
xcb_input_get_device_modifier_mapping_keymaps_end(const
xcb_input_get_device_modifier_mapping_reply_t *reply);
REQUEST ARGUMENTS
REPLY FIELDS
DESCRIPTIONRETURN VALUEReturns an xcb_input_get_device_modifier_mapping_cookie_t. Errors have to be handled when calling the reply function xcb_input_get_device_modifier_mapping_reply.If you want to handle errors in the event loop instead, use xcb_input_get_device_modifier_mapping_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. |