xcb_input_tou...ership_event_t(3)

💅 xcb_input_touch_ownership_event_t — from the XCB Events manual 💅

okay bestie, sit DOWN, because we're talking about xcb_input_touch_ownership_event_t, a whole entire event datastructure from the XCB Events section of the manual (section 3, if you're keeping score 🎀). yes the title has an ellipsis in it. no I don't know why. it's giving "my name got truncated by the terminal" energy and honestly? iconic.

✨ SYNOPSIS ✨

pull it in with:

#include <xcb/xinput.h>

🦋 Event datastructure 🦋

here's the struct, character for character, no notes, she's perfect:

typedef struct xcb_input_touch_ownership_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              touchid;
    xcb_window_t          root;
    xcb_window_t          event;
    xcb_window_t          child;
    uint32_t              full_sequence;
    xcb_input_device_id_t sourceid;
    uint8_t               pad0[2];
    uint32_t              flags;
    uint8_t               pad1[8];
} xcb_input_touch_ownership_event_t;

look at those pad bytes. pad0[2] and pad1[8]. they're not doing anything, they're just vibing, and honestly same. 💜

🌸 EVENT FIELDS 🌸

one by one, bestie, we go through every single one:

• response_type — this is the type of the event, and in this specific case it's XCB_INPUT_TOUCH_OWNERSHIP. it ALSO shows up in the xcb_generic_event_t, which is the whole reason you can tell your events apart from each other like 👀 "wait who are you". so yeah, crucial.
• sequence — the sequence number of the last request the X11 server actually processed. it's the server's little receipt number, no cap.
• extension — NOT YET DOCUMENTED. 😭
• length — NOT YET DOCUMENTED. 😭
• event_type — NOT YET DOCUMENTED. 😭
• deviceid — NOT YET DOCUMENTED. 😭
• time — NOT YET DOCUMENTED. 😭
• touchid — NOT YET DOCUMENTED. 😭
• root — NOT YET DOCUMENTED. 😭
• event — NOT YET DOCUMENTED. 😭
• child — NOT YET DOCUMENTED. 😭
• full_sequence — NOT YET DOCUMENTED. 😭
• sourceid — NOT YET DOCUMENTED. 😭
• flags — NOT YET DOCUMENTED. 😭

not me listing thirteen fields and eleven of them saying the same thing 💀 that's not a vibe check, that's a vibe crisis. the documentation said "I'll finish this later" and then never texted back. we still love her though 🫶

🧚 DESCRIPTION 🧚

so... there isn't one. this section is empty in the original. she left the group chat on read. ✨ nothing here, bestie, we move. ✨

🌈 SEE ALSO 🌈

also empty! zero cross-references, zero friends, zero links. main character energy fr fr, she doesn't need anyone else. 👑

💖 AUTHOR 💖

this page was generated from xinput.xml. if you clock a typo or you've got corrections and improvements, hit up xcb@lists.freedesktop.org — they want the feedback, periodt.

and that's the whole page, bestie! 💅 she's from X Version 11, she ships as part of libxcb 1.17.0, and that's a wrap on xcb_input_touch_ownership_event_t(3) — go forth, read your event structs, and slay. 🎀🦋💜