xcb_input_dev...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_dev...notify_event_t(3) πŸ’–

okay bestie, welcome to section 3 of the manual β€” this is one of the XCB Events pages, and today's main character is a little event struct with a truly unhinged number of NOT YET DOCUMENTED lines. we're gonna get through it together. 🫢


✨ NAME ✨

xcb_input_device_state_notify_event_t β€” that's it, that's the whole name, the manpage literally gives it a description shaped hole and honestly? relatable.


🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/xinput.h>

πŸŽ€ Event datastructure

here's the whole vibe, character for character, no cap:

typedef struct xcb_input_device_state_notify_event_t {
    uint8_t         response_type;
    uint8_t         device_id;
    uint16_t        sequence;
    xcb_timestamp_t time;
    uint8_t         num_keys;
    uint8_t         num_buttons;
    uint8_t         num_valuators;
    uint8_t         classes_reported;
    uint8_t         buttons[4];
    uint8_t         keys[4];
    uint32_t        valuators[3];
} xcb_input_device_state_notify_event_t;

she's structured, she's typed, she's giving very much fixed-size-arrays-and-a-timestamp energy. πŸ’…


πŸ”₯ EVENT FIELDS πŸ”₯

  • response_type β€” the type of this event, and in this case it's XCB_INPUT_DEVICE_STATE_NOTIFY. this field is also chillin' in the xcb_generic_event_t, which is the whole point: it's how you tell your events apart from each other. one field, so many responsibilities. main character behaviour fr fr.
  • sequence β€” the sequence number of the last request processed by the X11 server. it's the receipts. keep track of it. 🧾
  • device_id β€” NOT YET DOCUMENTED. 😭
  • time β€” NOT YET DOCUMENTED. 😭
  • num_keys β€” NOT YET DOCUMENTED. 😭
  • num_buttons β€” NOT YET DOCUMENTED. 😭
  • num_valuators β€” NOT YET DOCUMENTED. 😭
  • classes_reported β€” NOT YET DOCUMENTED. 😭
  • buttons β€” NOT YET DOCUMENTED. 😭
  • keys β€” NOT YET DOCUMENTED. 😭
  • valuators β€” NOT YET DOCUMENTED. 😭
bestie. that is nine fields in a row that are NOT YET DOCUMENTED. not me reading this like it's a group chat where everyone left me on read πŸ’€ we're just relaying the facts here β€” the source says what the source says, and it says nothing about these. i'm not gonna make stuff up for you, that's not the move. πŸ™ˆ

πŸ¦‹ DESCRIPTION πŸ¦‹

so... this section is empty. like, empty empty. there is no description in the original, so there's no description here. she's mysterious. she's elusive. she's keeping secrets. ⭐


🌈 SEE ALSO 🌈

also empty! nothing to see here, literally. no cross-references were provided, so i'm not inventing any β€” you get exactly zero of them, and that's the honest count. πŸ’œ


πŸ‘‘ AUTHOR πŸ‘‘

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

like, if something's wrong or missing, please email them, because clearly some fields are still waiting for their glow-up. πŸ“§βœ¨


and that's the page!! thanks for coming to my ted talk, ily, stay hydrated, go read your structs πŸ’–

sign-off: this one came to you from X Version 11, rocking libxcb 1.17.0 β€” that's the whole footer, and honestly it deserved a shoutout instead of getting squished at the bottom of a terminal. slay. πŸŽ€βœ¨πŸ¦‹