xcb_xkb_get_kbd_by_name_unchecked3
Part of xcb_xkb_get_kbd_by_name(3).
Usage
Reply datastructure
uint8_t response_type;
uint8_t deviceID;
uint16_t sequence;
uint32_t length;
xcb_keycode_t minKeyCode;
xcb_keycode_t maxKeyCode;
uint8_t loaded;
uint8_t newKeyboard;
uint16_t found;
uint16_t reported;
uint8_t pad0
[16]
;
Reply accessors
xcb_xkb_get_kbd_by_name_replies_t *xcb_xkb_get_kbd_by_name_replies
(const
xcb_xkb_get_kbd_by_name_request_t
*reply)
Request arguments
- conn
-
The XCB connection to X11.
- deviceSpec
-
TODO: NOT YET DOCUMENTED.
- need
-
TODO: NOT YET DOCUMENTED.
- want
-
TODO: NOT YET DOCUMENTED.
- load
-
TODO: NOT YET DOCUMENTED.
Reply fields
- response_type
-
The type of this reply, in this case XCB_XKB_GET_KBD_BY_NAME. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other.
- sequence
-
The sequence number of the last request processed by the X11 server.
- length
-
The length of the reply, in words (a word is 4 bytes).
- deviceID
-
TODO: NOT YET DOCUMENTED.
- minKeyCode
-
TODO: NOT YET DOCUMENTED.
- maxKeyCode
-
TODO: NOT YET DOCUMENTED.
- loaded
-
TODO: NOT YET DOCUMENTED.
- newKeyboard
-
TODO: NOT YET DOCUMENTED.
- found
-
TODO: NOT YET DOCUMENTED.
- reported
-
TODO: NOT YET DOCUMENTED.
Overview
Return value
Returns an xcb_xkb_get_kbd_by_name_cookie_t. Errors have to be handled when calling the reply function xcb_xkb_get_kbd_by_name_reply.
If you want to handle errors in the event loop instead, use xcb_xkb_get_kbd_by_name_unchecked. See xcb-requests(3) for details.
Errors
This request does never generate any errors.
History
- Arch Linux 2026-11-01 to Debian 13 (Trixie): the text shown here
- Debian 12 (Bookworm)
- Debian 11 (Bullseye)
- Debian 10 (Buster)
- Debian 9 (Stretch)