xcb_circulate_notify_event_t(3)

💅 xcb_circulate_notify_event_t — bestie, it's an event struct 🎀

okay so real talk, this is page xcb_circulate_notify_event_t(3) from the XCB Events section of the manual, and bestie... the docs are giving "we'll get to it" 😭. The NAME literally says NOT YET DOCUMENTED. Not me showing up to the group chat with a whole struct and zero explanation 💀. But we're gonna read every single field anyway because that's just who we are. ✨

🌸 NAME 🌸

xcb_circulate_notify_event_t — NOT YET DOCUMENTED</p> 🙈 (yes fr, that's the whole thing, the maintainers are edging us)

🦋 SYNOPSIS 🦋

#include <xcb/xproto.h>

💖 Event datastructure 💖

typedef struct xcb_circulate_notify_event_t {
    uint8_t      response_type;
    uint8_t      pad0;
    uint16_t     sequence;
    xcb_window_t event;
    xcb_window_t window;
    uint8_t      pad1[4];
    uint8_t      place;
    uint8_t      pad2[3];
} xcb_circulate_notify_event_t;

look at her. she's structured. she's aligned. she has three separate padding arrays because the X11 wire format said "we're gonna be a specific number of bytes and you WILL respect it" 👑 no cap.

✨ EVENT FIELDS ✨

• response_type — the type of this event, and in this case it's XCB_CIRCULATE_REQUEST. this field is also chillin' inside xcb_generic_event_t, so you can use it to tell your events apart from each other when they're all just vibing in one queue. it's the name tag at the party 🎀
• sequence — the sequence number of the last request the X11 server processed. think of it like a receipt number for your requests, so you know exactly how far the server got 🧾
• event — this one's the restacked window or its parent, depending on whether you selected StructureNotify or SubstructureNotify. so it's giving "it depends on your subscription, babe" 💅
• window — the restacked window. no asterisk, no caveat, no it depends. just the restacked window. iconic. ⭐
• place — (silence) 🦗 okay so the manpage gives us literally nothing here. the field exists. it is a uint8_t. that's all we get, bestie. iykyk 😭

💜 DESCRIPTION 💜

there is no description. the section is empty. we are simply left on read 💀

not a single word of prose. not one. if you needed lore, this page is not the one — go ask xcb_circulate_window(3) what's actually going on 🫶

🌈 SEE ALSO 🌈

• xcb_generic_event_t(3) — the generic event that carries our girl's response_type field around 🎀
• xcb_circulate_window(3) — the request that makes this notification even happen in the first place 🔥

💌 AUTHOR 💌

generated from xproto.xml. want corrections or improvements? hit up xcb@lists.freedesktop.org — they're literally asking for it, fr fr 💖

and that's the whole page, bestie!! shoutout to X Version 11 and libxcb 1.17.0 for bringing us this gorgeous little struct with the world's most mysterious place field 🦋 mwah, take care of your padding arrays, drink water, and always check your response_type before you cast 💅✨