xcb_input_cha...yboard_device(3)
π¦ NAME π¦
xcb_input_change_keyboard_device β okay so this is the XCB request that swaps which keyboard device is the keyboard device, bestie π
It lives in the XCB Requests manual, and it's giving "I only exist so you can change the keyboard device and nothing else" energy. Iconic, honestly.
β¨ SYNOPSIS β¨
First things first, you gotta pull in the header, no cap:
#include <xcb/xinput.h>
π Request function
xcb_input_change_keyboard_device_cookie_t
xcb_input_change_keyboard_device(xcb_connection_t *conn,
uint8_t device_id);
π Reply datastructure
typedef struct xcb_input_change_keyboard_device_reply_t {
uint8_t response_type;
uint8_t xi_reply_type;
uint16_t sequence;
uint32_t length;
uint8_t status;
uint8_t pad0[23];
} xcb_input_change_keyboard_device_reply_t;
πΈ Reply function
xcb_input_change_keyboard_device_reply_t
*xcb_input_change_keyboard_device_reply(xcb_connection_t *conn,
xcb_input_change_keyboard_device_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. Your lil hotline to the server, fr fr. π«Άdevice_idβ TODO: NOT YET DOCUMENTED. Yeah bestie, that's literally all it says. The lore is unfinished. π
π REPLY FIELDS π
response_typeβ the type of this reply, which in this case isXCB_INPUT_CHANGE_KEYBOARD_DEVICE. This field is also chillin' inside thexcb_generic_reply_t, so you can use it to tell replies apart from each other. Vibe check: passed. βsequenceβ the sequence number of the last request processed by the X11 server. Keeping receipts, as she should. π§Ύlengthβ the length of the reply, in words (and a word here is4bytes, just so we're clear). πxi_reply_typeβ TODO: NOT YET DOCUMENTED. Mystery field, we simply don't know her. πstatusβ TODO: NOT YET DOCUMENTED. Also a mystery. The girls are keeping secrets. π
π DESCRIPTION π
Nothing here. The original page has literally no description text. Not one word. We're all just vibing off the SYNOPSIS alone, and that's fine. π
π₯ RETURN VALUE π₯
She hands you back an xcb_input_change_keyboard_device_cookie_t. Errors have to be handled when you call the reply function xcb_input_change_keyboard_device_reply.
If you'd rather handle errors in the event loop instead, use xcb_input_change_keyboard_device_unchecked. See xcb-requests(3) for the details, bestie β that's where the real tea is. β
π ERRORS π
This request does never generate any errors. Not a single one. She's unproblematic, she's drama-free, she simply does not start anything. β¨
πΈ SEE ALSO πΈ
Empty. Nothing to see here. No cross-references, no friends, just her. Main character energy, honestly. π
π«Ά AUTHOR π«Ά
Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. If you find a typo, tell them, not me. π
And that's the whole page, bestie!! This absolute gem comes from X Version 11, libxcb 1.17.0 β so yeah, that's the source and the version, consider yourself informed. πβ¨π Go forth and change a keyboard device, or whatever. Slay. π π¦
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms