xcb_input_button_press_event_t(3)

💖 xcb_input_button_press_event_t 💖

okay so bestie, welcome to the libxcb corner of the X11 universe — this one lives in the XCB Events manual, section 3, and it's literally just the event struct for input button presses. yes, the NAME section is genuinely just the name with a lil dash and nothing after it, no cap, they left the description slot empty. we move.

✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xinput.h>

🦋 Event datastructure 🦋

here's the whole struct, character for character, don't let anyone tell you otherwise:

typedef struct xcb_input_button_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_window_t              root;
    xcb_window_t              event;
    xcb_window_t              child;
    uint32_t                  full_sequence;
    xcb_input_fp1616_t        root_x;
    xcb_input_fp1616_t        root_y;
    xcb_input_fp1616_t        event_x;
    xcb_input_fp1616_t        event_y;
    uint16_t                  buttons_len;
    uint16_t                  valuators_len;
    xcb_input_device_id_t     sourceid;
    uint8_t                   pad0[2];
    uint32_t                  flags;
    xcb_input_modifier_info_t mods;
    xcb_input_group_info_t    group;
} xcb_input_button_press_event_t;

👑 EVENT FIELDS 👑

time to vibe check every single member, one by one, no skips:

• response_type — the type of this event, in this case XCB_INPUT_MOTION. this field is also present in the xcb_generic_event_t and can be used to tell events apart from each other. (yes the docs really say XCB_INPUT_MOTION on the button-press page. iconic of them. we're reporting it exactly as written, don't shoot the messenger 💀)
• sequence — the sequence number of the last request processed by the X11 server.
• 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.
• root — NOT YET DOCUMENTED.
• event — NOT YET DOCUMENTED.
• child — NOT YET DOCUMENTED.
• full_sequence — NOT YET DOCUMENTED.
• root_x — NOT YET DOCUMENTED.
• root_y — NOT YET DOCUMENTED.
• event_x — NOT YET DOCUMENTED.
• event_y — NOT YET DOCUMENTED.
• buttons_len — NOT YET DOCUMENTED.
• valuators_len — NOT YET DOCUMENTED.
• sourceid — NOT YET DOCUMENTED.
• flags — NOT YET DOCUMENTED.
• mods — NOT YET DOCUMENTED.
• group — NOT YET DOCUMENTED.

ngl the "NOT YET DOCUMENTED" era is giving unfinished group project energy 😭 but that's genuinely all the page says for those fields, so that's what you get. no inventing lore, bestie, we keep it real.

🌈 DESCRIPTION 🌈

...so the DESCRIPTION section is empty. completely. a blank canvas. main character silence. there is literally nothing here, and we are not about to make stuff up about it. periodt. 🎀

🔥 SEE ALSO 🔥

also empty, bestie. nothing referenced, nothing linked, just vibes and a whole lot of blank space. 🦋

💜 AUTHOR 💜

generated from xinput.xml. contact xcb@lists.freedesktop.org for corrections and improvements — so if something's off, that's your girl to email, fr fr. ✨

and that's the whole page! this was X Version 11, libxcb 1.17.0, and you absolutely ate reading a struct definition all the way to the end, i'm obsessed 🫶💅