XCB_INPUT_GET_DEVICE_BUTTON_MAPPING(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

💅 xcb_input_get_device_button_mapping — the tea ☕

okay bestie, welcome to xcb_input_get_device_button_mapping, a lil' request from xcb_input_get...button_mapping(3) (that's the manual name, she's long, we love her). this one's for when you wanna peek at how a device's buttons are mapped. no cap. ✨

🌸 NAME 🌸

xcb_input_get_device_button_mapping — (the original page is shy and leaves this blank, and honestly? we respect the mystery 🫶)

✨ SYNOPSIS ✨

#include <xcb/xinput.h>

🎀 Request function

xcb_input_get_device_button_mapping_cookie_t
       xcb_input_get_device_button_mapping(xcb_connection_t *conn,
       uint8_t device_id);

🦋 Reply datastructure

typedef struct xcb_input_get_device_button_mapping_reply_t {
    uint8_t  response_type;
    uint8_t  xi_reply_type;
    uint16_t sequence;
    uint32_t length;
    uint8_t  map_size;
    uint8_t  pad0[23];
} xcb_input_get_device_button_mapping_reply_t;

💖 Reply function

xcb_input_get_device_button_mapping_reply_t
       *xcb_input_get_device_button_mapping_reply(xcb_connection_t *conn,
       xcb_input_get_device_button_mapping_cookie_t cookie,
       xcb_generic_error_t **e);

🌈 Reply accessors

uint8_t *xcb_input_get_device_button_mapping_map(const
       xcb_input_get_device_button_mapping_request_t *reply);

int xcb_input_get_device_button_mapping_map_length(const
       xcb_input_get_device_button_mapping_reply_t *reply);

xcb_generic_iterator_t xcb_input_get_device_button_mapping_map_end(const
       xcb_input_get_device_button_mapping_reply_t *reply); uint8_t
       *xcb_input_get_device_button_mapping_pad_1 (const
       xcb_input_get_device_button_mapping_request_t *reply)

👑 REQUEST ARGUMENTS 👑

  • conn — the XCB connection to X11, your main character link to the server 💫
  • device_id — TODO: NOT YET DOCUMENTED. (the manpage literally said that, bestie, we're just being honest 🫠)

💀 REPLY FIELDS 💀

  • response_type — the type of this reply, and in this case it's XCB_INPUT_GET_DEVICE_BUTTON_MAPPING. this field also lives in the xcb_generic_reply_t so you can tell your replies apart from each other, very "who is she" energy 🔍
  • sequence — the sequence number of the last request processed by the X11 server. keeping receipts, fr fr 🧾
  • length — the length of the reply, in words. and reminder: a word is 4 bytes 💅
  • xi_reply_type — TODO: NOT YET DOCUMENTED. 🫥
  • map_size — TODO: NOT YET DOCUMENTED. 🫥

🍓 DESCRIPTION 🍓

...the original page has nothing here. literally nothing. an empty section, a vibe, a blank canvas. we're keeping it exactly as iconic (and as empty) as it was ✨

🔥 RETURN VALUE 🔥

Returns an xcb_input_get_device_button_mapping_cookie_t. that's your lil' cookie, hold onto her 🍪

Errors have to be handled when you call the reply function xcb_input_get_device_button_mapping_reply.

If you'd rather handle errors in the event loop instead, use xcb_input_get_device_button_mapping_unchecked. See xcb-requests(3) for details, iykyk 📖

😭 ERRORS 😭

This request does never generate any errors. not one. zero. she's unproblematic, she's at peace, we stan 🌸

💜 SEE ALSO 💜

(no entries on the original page — an empty section, and we're honoring it, periodt)

🫶 AUTHOR 🫶

Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 💌

and that's the whole page, bestie!! this one came from X Version 11, libxcb 1.17.0 💖 slay, go map some buttons, you've got this 💖

📦 where this page comes from