xcb_input_enter_event_t(3)

💖 xcb_input_enter_event_t 💖

okay bestie, so this is a page from the XCB Events manual — yeah, the xcb_input_enter_event_t one, the enter event datastructure for X Input. it's giving "pointer walks into a window and the server has OPINIONS about it" ✨

🌸 NAME 🌸

xcb_input_enter_event_t — the enter event datastructure. that's it. that's the name. (the og page left the description blank, so we're keeping it blank, no cap 🫶)

✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xinput.h>

🎀 Event datastructure 🎀

here's the whole struct, every single field, exactly as it lives, do not touch, do not rename, do not breathe on it 💅

typedef struct xcb_input_enter_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;
    xcb_input_device_id_t     sourceid;
    uint8_t                   mode;
    uint8_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;
    uint8_t                   same_screen;
    uint8_t                   focus;
    uint16_t                  buttons_len;
    xcb_input_modifier_info_t mods;
    xcb_input_group_info_t    group;
} xcb_input_enter_event_t;

like. look at her. twenty-three fields and not one of them is optional. iconic behavior honestly 👑

🦋 EVENT FIELDS 🦋

okay so field by field, and I'm gonna be real with you: a lot of this page is NOT YET DOCUMENTED, and I am NOT about to make stuff up, so those stay NOT YET DOCUMENTED. the mystery is part of the aesthetic ✨

• response_type — the type of this event, and in this case it's XCB_INPUT_FOCUS_OUT. this field also lives inside xcb_generic_event_t, so you can use it to tell your events apart from each other. (yes, it says XCB_INPUT_FOCUS_OUT on the enter event page. that's what the og says, so that's what we're saying. iykyk 😭)
• sequence — the sequence number of the last request the X11 server processed.
• extension — NOT YET DOCUMENTED.
• length — NOT YET DOCUMENTED.
• event_type — NOT YET DOCUMENTED.
• deviceid — NOT YET DOCUMENTED.
• time — NOT YET DOCUMENTED.
• sourceid — NOT YET DOCUMENTED.
• mode — 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.
• same_screen — NOT YET DOCUMENTED.
• focus — NOT YET DOCUMENTED.
• buttons_len — NOT YET DOCUMENTED.
• mods — NOT YET DOCUMENTED.
• group — NOT YET DOCUMENTED.

💀 bestie there are SO many blanks here. that's not me being lazy, that's genuinely what the page says. the struct is fully specified, the field docs are just... still loading. girl help 🙈

💜 DESCRIPTION 💜

...and that's it. the section is empty in the original. literally nothing here. a whole heading with no content, main character energy with zero dialogue 🌈

🌟 SEE ALSO 🌟

also empty. no cross-references. she's mysterious like that 🧚

👑 AUTHOR 👑

generated from xinput.xml. if you spot something wrong or wanna make it better, hit up xcb@lists.freedesktop.org with corrections and improvements. they're listening, fr fr 🫶

and that's the whole page, bestie!! 💖 this one came out of X Version 11, libxcb 1.17.0, and it lives in the XCB Events manual, filed under xcb_input_enter_event_t(3). go forth and read your enter events. slay 🎀✨💅