XCB_INPUT_RAW_KEY_PRESS_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_raw_key_press_event_t πŸ’–

okay so bestie, welcome to xcb_input_raw_key_press_event_t(3), straight out of the XCB Events corner of the manual. it's giving "struct that holds one raw key press event" and honestly? we're obsessed. let's get into it 🫢


✨ NAME ✨

xcb_input_raw_key_press_event_t β€” literally just the name, that's it, the manpage left it at that πŸ’…


✨ SYNOPSIS ✨

first up, you gotta bring in the header, no cap:

#include <xcb/xinput.h>

πŸ¦‹ Event datastructure πŸ¦‹

and here's the whole struct, character for character, do not freestyle this one:

typedef struct xcb_input_raw_key_press_event_t {
    uint8_t               response_type;
    uint8_t               extension;
    uint16_t              sequence;
    uint32_t              length;
    uint16_t              event_type;
    xcb_input_device_id_t deviceid;
    xcb_timestamp_t       time;
    uint32_t              detail;
    xcb_input_device_id_t sourceid;
    uint16_t              valuators_len;
    uint32_t              flags;
    uint8_t               pad0[4];
    uint32_t              full_sequence;
} xcb_input_raw_key_press_event_t;

🌸 EVENT FIELDS 🌸

okay so here's the field-by-field breakdown, and yes we're going through every single one, no skipping, we don't do that here πŸ’–

  • response_type β€” the type of this event, and in this case it's XCB_INPUT_RAW_KEY_RELEASE. (iconic little plot twist there, we simply report it as written ✨) this field also lives in the xcb_generic_event_t, so you can use it to tell your events apart from each other. very main character of it.
  • sequence β€” the sequence number of the last request that got processed by the X11 server. it's the receipts, basically 🧾
  • extension β€” NOT YET DOCUMENTED. 😭
  • length β€” NOT YET DOCUMENTED. 😭
  • event_type β€” NOT YET DOCUMENTED. 😭
  • deviceid β€” NOT YET DOCUMENTED. 😭
  • time β€” NOT YET DOCUMENTED. 😭
  • detail β€” NOT YET DOCUMENTED. 😭
  • sourceid β€” NOT YET DOCUMENTED. 😭
  • valuators_len β€” NOT YET DOCUMENTED. 😭
  • flags β€” NOT YET DOCUMENTED. 😭
  • full_sequence β€” NOT YET DOCUMENTED. 😭
bestie the manpage really said "mystery" for like eleven fields in a row and honestly? we respect the honesty. lowkey a whole vibe. πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

so… there's a DESCRIPTION section. and it is empty. nothing. a whole heading with no text under it. not me getting emotionally attached to a blank section 😭


πŸŽ€ SEE ALSO πŸŽ€

and the SEE ALSO section? also empty. no references. no siblings. no nothing. it's giving lone wolf energy 🐺✨


🌈 AUTHOR 🌈

generated from xinput.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're accepting notes fr fr 🫢


and that's the whole page, bestie!! X Version 11, libxcb 1.17, and this lil cutie of a manpage said its goodbyes right there on the last line. mwah πŸ’…βœ¨πŸ’–