XCB_INPUT_SET_DEVICE_BUTTON_MAPPING_UNCHECKED(3)
β¨ NAME β¨
xcb_input_set_device_button_mapping β bestie... the description slot is literally empty π the manpage just leaves a lil dash hanging there with nothing after it. Iconic of it, honestly.
πΈ SYNOPSIS πΈ
First things first, you gotta pull in the header:
#include <xcb/xinput.h>
π Request function
xcb_input_set_device_button_mapping_cookie_t
xcb_input_set_device_button_mapping(xcb_connection_t *conn,
uint8_t device_id, uint8_t map_size, const uint8_t *map);
π¦ Reply datastructure
typedef struct xcb_input_set_device_button_mapping_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_set_device_button_mapping_reply_t;
π Reply function
xcb_input_set_device_button_mapping_reply_t
*xcb_input_set_device_button_mapping_reply(xcb_connection_t *conn,
xcb_input_set_device_button_mapping_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11, your lil hotline to the server πdevice_idβ TODO: NOT YET DOCUMENTED. yeah bestie, they left it blank πmap_sizeβ TODO: NOT YET DOCUMENTED. also blank, we love a mystery β¨mapβ TODO: NOT YET DOCUMENTED. blank blank blank, the trio of unknown π
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_INPUT_SET_DEVICE_BUTTON_MAPPING. this same field also lives insidexcb_generic_reply_t, so you can use it to tell your replies apart from each other πsequenceβ the sequence number of the last request the X11 server processed, fr frlengthβ how long the reply is, in words (and a word here = 4 bytes, no cap)xi_reply_typeβ TODO: NOT YET DOCUMENTED. mystery field, we don't know her π«Άstatusβ TODO: NOT YET DOCUMENTED. also unknown, also slaying in silence π
β DESCRIPTION β
literally nothing here. the DESCRIPTION section is empty, bestie. not a single word. the void ate it. π
π§ RETURN VALUE π§
You get back an xcb_input_set_device_button_mapping_cookie_t. errors? those get handled when you call the reply function xcb_input_set_device_button_mapping_reply.
If you'd rather deal with errors in the event loop instead, use xcb_input_set_device_button_mapping_unchecked. peep xcb-requests(3) for the deets π
π ERRORS π
This request does never generate any errors. zero. none. clean record, main character energy π₯
π SEE ALSO π
nothing listed here either β the SEE ALSO section is just vibes and silence. πΈ
π AUTHOR π
Generated from xinput.xml. got corrections or improvements? hit up xcb@lists.freedesktop.org β they're taking notes π
okay and that's the whole page bestie!! π«Ά this was xcb_input_set...button_mapping(3) from the XCB Requests manual, brought to you by X Version 11 and libxcb 1.17.0. go forth and map those buttons, mwah πβ¨
π¦ 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