xcb_present_r...notify_event_t(3)

💖 xcb_present_redirect_notify_event_t 💖

okay bestie, so this is a page from the XCB Events manual — it's xcb_present_r...notify_event_t(3), and yes the title got chopped mid-word like that, that's just how it lives, no cap. It's all about the xcb_present_redirect_notify_event_t event datastructure from <xcb/present.h>. Present as in the Present extension. Redirect notify as in ✨the server is telling you something happened with a redirected window✨. We're so back.

🌸 NAME 🌸

xcb_present_redirect_notify_event_t — and then a dash, and then nothing, because the original page left it blank. The dash is iconic. The void after it is also iconic. 🫶

✨ SYNOPSIS ✨

First, you gotta include the header, obviously:

#include <xcb/present.h>

🎀 Event datastructure 🎀

here's the whole struct, copied exactly, don't touch a single byte bestie:

typedef struct xcb_present_redirect_notify_event_t {
    uint8_t             response_type;
    uint8_t             extension;
    uint16_t            sequence;
    uint32_t            length;
    uint16_t            event_type;
    uint8_t             update_window;
    uint8_t             pad0;
    xcb_present_event_t event;
    xcb_window_t        event_window;
    xcb_window_t        window;
    xcb_pixmap_t        pixmap;
    uint32_t            serial;
    uint32_t            full_sequence;
    xcb_xfixes_region_t valid_region;
    xcb_xfixes_region_t update_region;
    xcb_rectangle_t     valid_rect;
    xcb_rectangle_t     update_rect;
    int16_t             x_off;
    int16_t             y_off;
    xcb_randr_crtc_t    target_crtc;
    xcb_sync_fence_t    wait_fence;
    xcb_sync_fence_t    idle_fence;
    uint32_t            options;
    uint8_t             pad1[4];
    uint64_t            target_msc;
    uint64_t            divisor;
    uint64_t            remainder;
} xcb_present_redirect_notify_event_t;

🔥 EVENT FIELDS 🔥

listen, most of these are literally "NOT YET DOCUMENTED" in the original, and I am NOT about to make up lore that isn't there. So the honest-to-god answer for a lot of these is: nobody wrote it down yet. I'm passing that truth along verbatim, bestie. 💀

• response_type — the type of this event, and in this specific case it's XCB_PRESENT_REDIRECT_NOTIFY. it also shows up in the xcb_generic_event_t, which is how you tell one event apart from another. your little ID badge. 💅
• sequence — the sequence number of the last request that got processed by the X11 server.
• extension — NOT YET DOCUMENTED.
• length — NOT YET DOCUMENTED.
• event_type — NOT YET DOCUMENTED.
• update_window — NOT YET DOCUMENTED.
• event — NOT YET DOCUMENTED.
• event_window — NOT YET DOCUMENTED.
• window — NOT YET DOCUMENTED.
• pixmap — NOT YET DOCUMENTED.
• serial — NOT YET DOCUMENTED.
• full_sequence — NOT YET DOCUMENTED.
• valid_region — NOT YET DOCUMENTED.
• update_region — NOT YET DOCUMENTED.
• valid_rect — NOT YET DOCUMENTED.
• update_rect — NOT YET DOCUMENTED.
• x_off — NOT YET DOCUMENTED.
• y_off — NOT YET DOCUMENTED.
• target_crtc — NOT YET DOCUMENTED.
• wait_fence — NOT YET DOCUMENTED.
• idle_fence — NOT YET DOCUMENTED.
• options — NOT YET DOCUMENTED.
• target_msc — NOT YET DOCUMENTED.
• divisor — NOT YET DOCUMENTED.
• remainder — NOT YET DOCUMENTED.

lowkey a mood that the field list is 90% "NOT YET DOCUMENTED" and 10% vibes, but that's the canon, and I'm not inventing anything. 🧚

💜 DESCRIPTION 💜

...yeah. there isn't one. the DESCRIPTION section is empty in the original. no prose, no explanation, just silence and the faint sound of a struct existing. it's giving minimalism. it's giving "the documentation is in the source code, bestie". 😭

🦋 SEE ALSO 🦋

...also empty! no cross-references, no friends, no SEE ALSO squad. this page is a solo act. main character energy, honestly. 👑

🎀 AUTHOR 🎀

generated from present.xml. if you spot something wrong or wanna improve it, contact xcb@lists.freedesktop.org — that's the official "hey this is busted" hotline. 📧

and that's the whole page, bestie! it was X Version 11, from libxcb 1.17.0, and it lives at xcb_present_r...notify_event_t(3). go forth, read your struct, tell the X server what's up. slay, periodt. 💅✨🌈