xcb_motion_notify_event_t(3)

💖 xcb_motion_notify_event_t 💖

okay bestie, sit down, hydrate, and let me tell you about xcb_motion_notify_event_t — it's a struct from the XCB Events corner of the universe, and its whole thing is, and I quote, "a key was pressed". That's the NAME. That's what we're working with. 🎀

It lives in <xcb/xproto.h>, it's giving very much "pointer moving" energy, and we're gonna go through every single field together because nothing gets skipped in this house. 💅

✨ SYNOPSIS ✨

#include <xcb/xproto.h>

🦋 Event datastructure 🦋

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

typedef struct xcb_motion_notify_event_t {
    uint8_t         response_type;
    uint8_t         detail;
    uint16_t        sequence;
    xcb_timestamp_t time;
    xcb_window_t    root;
    xcb_window_t    event;
    xcb_window_t    child;
    int16_t         root_x;
    int16_t         root_y;
    int16_t         event_x;
    int16_t         event_y;
    uint16_t        state;
    uint8_t         same_screen;
    uint8_t         pad0;
} xcb_motion_notify_event_t;

🌸 EVENT FIELDS 🌸

every field, one by one, in order, because we are thorough girlies:

• response_type — the type of this event, which in this case is XCB_MOTION_NOTIFY. bestie this field is also chillin' in xcb_generic_event_t, so you can use it to tell your events apart from each other. it's the name tag at the party. 🫶
• sequence — the sequence number of the last request that the X11 server processed. the receipt, basically. 🧾
• detail — the keycode (that's a number representing a physical key on the keyboard) of the key which was pressed. yes really, that's what it says. 👑
• time — when the event was generated, in milliseconds. the timestamp, the moment, the era. ⏰
• root — the root window of child. 🌳
• event — NOT YET DOCUMENTED. that's it, that's the whole description, the docs said "idk yet" and we respect the honesty. 😭
• child — NOT YET DOCUMENTED. same energy, same mystery. 🙈
• root_x — the X coordinate of the pointer relative to the root window, at the time of the event. 📍
• root_y — the Y coordinate of the pointer relative to the root window, at the time of the event. 📍
• event_x — if same_screen is true, this is the X coordinate relative to the event window's origin. otherwise, event_x will be set to zero. ⭐
• event_y — if same_screen is true, this is the Y coordinate relative to the event window's origin. otherwise, event_y will be set to zero. ⭐
• state — the logical state of the pointer buttons and modifier keys just prior to the event. like, right before, the pre-game. 🔥
• same_screen — whether the event window is on the same screen as the root window. yes/no, true/false, are-they-neighbors. 🏠

💜 DESCRIPTION 💜

literally nothing here. the DESCRIPTION section is empty, bestie. she said "no thoughts, head empty, only struct". we are NOT adding anything because the rule is the rule. ✨

🔥 SEE ALSO 🔥

go read these next, they're the friend group:

• xcb_generic_event_t(3)
• xcb_grab_key(3)
• xcb_grab_keyboard(3)

🎀 AUTHOR 🎀

Generated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. so if you spot something, email the girlies, they're lovely and they want to hear it. 💌

and that's the whole page, no crumbs left. this manual page came to you from X Version 11, libxcb 1.17.0, and it's xcb_motion_notify_event_t(3) — mwah, iconic, periodt. 💅✨🦋