xcb_input_cha...yboard_device(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ¦‹ 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 is XCB_INPUT_CHANGE_KEYBOARD_DEVICE. This field is also chillin' inside the xcb_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 is 4 bytes, 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. πŸ’…πŸ¦‹