XCB_INPUT_DEVICE_BUTTON_STATE_NOTIFY_EVENT_T(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_device_button_state_notify_event_t(3) 💖

okay bestie, so this is an XCB Events page from section 3 of the manual — yes, the whole xcb_input_devi...notify_event_t family, the one with the dramatic ellipsis in the header. we're talking about xcb_input_device_button_state_notify_event_t, and honestly? it's giving "small struct, big feelings". let's get into it 🫶

✨ NAME ✨

xcb_input_device_button_state_notify_event_t — (yeah, the original literally leaves it at that, no explanation, iconic mysterious energy 💅)

🌸 SYNOPSIS 🌸

#include <xcb/xinput.h>

🦋 Event datastructure

typedef struct xcb_input_device_button_state_notify_event_t {
    uint8_t  response_type;
    uint8_t  device_id;
    uint16_t sequence;
    uint8_t  buttons[28];
} xcb_input_device_button_state_notify_event_t;

like. look at her. four fields, one of them is 28 whole bytes of buttons. she's compact, she's tidy, she's serving 🎀

🔥 EVENT FIELDS 🔥

  • response_type — the type of this event, and in this case it's XCB_INPUT_DEVICE_BUTTON_STATE_NOTIFY. this field is also present in the xcb_generic_event_t, so you can use it to tell events apart from each other. it's the little name tag at the party so you know who just walked in 💖
  • sequence — the sequence number of the last request processed by the X11 server. your receipt number, basically 🧾✨
  • device_id — NOT YET DOCUMENTED. no cap, the manpage really just says that. we know nothing. she's a mystery 🙈
  • buttons — NOT YET DOCUMENTED. also a mystery. 28 bytes of pure undisclosed potential 💀

🌈 DESCRIPTION 🌈

(empty. literally nothing here. the original said nothing and honestly? respect. sometimes the vibe is silence ✨)

👑 SEE ALSO 👑

(also empty — there are no SEE ALSO references on this page, bestie, so don't go looking for cross-links that aren't there 🦋)

💜 AUTHOR 💜

generated from xinput.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they're literally waiting for your notes 🫶

and that's the whole page, periodt 💅 this was X Version 11, from libxcb 1.17, and yeah the footer date situation is exactly as mysterious as the device_id field. stay slaying, stay documenting the undocumented 🌸⭐

📦 where this page comes from