XCB_RANDR_SCREEN_CHANGE_NOTIFY_EVENT_T(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– xcb_randr_screen_change_notify_event_t β€” the manual, but make it make sense πŸ’–

okay bestie, so this is a page from XCB Events (that's the manual section it lives in), and it's about one very specific little struct: xcb_randr_screen_change_notify_event_t. she's an event datastructure. she's giving RandR screen change. she has a LOT of fields. let's get into it ✨


🌈 SYNOPSIS 🌈

first things first, you gotta bring her in:

#include <xcb/randr.h>

πŸŽ€ Event datastructure

here's the whole glow-up, every field, exactly as she is:

typedef struct xcb_randr_screen_change_notify_event_t {
    uint8_t         response_type;
    uint8_t         rotation;
    uint16_t        sequence;
    xcb_timestamp_t timestamp;
    xcb_timestamp_t config_timestamp;
    xcb_window_t    root;
    xcb_window_t    request_window;
    uint16_t        sizeID;
    uint16_t        subpixel_order;
    uint16_t        width;
    uint16_t        height;
    uint16_t        mwidth;
    uint16_t        mheight;
} xcb_randr_screen_change_notify_event_t;

that's her. that's the whole struct. iconic honestly πŸ’…


✨ EVENT FIELDS ✨

okay so field by field, let's vibe check each one πŸ¦‹

  • response_type β€” this tells you what kind of event you're looking at. in this case it's XCB_RANDR_SCREEN_CHANGE_NOTIFY. and here's the cute part: this field also lives inside xcb_generic_event_t, so you can peek at it there to figure out which event is which when they're all hanging out together. very "how do you do, fellow events" of her.
  • sequence β€” the sequence number of the last request that got processed by the X11 server. like a receipt number for the server's last move 🧾
  • rotation β€” NOT YET DOCUMENTED. yeah. she's a mystery. no cap.
  • timestamp β€” NOT YET DOCUMENTED. πŸ™ˆ
  • config_timestamp β€” NOT YET DOCUMENTED. πŸ’€
  • root β€” NOT YET DOCUMENTED. 😭
  • request_window β€” NOT YET DOCUMENTED. 🫢
  • sizeID β€” NOT YET DOCUMENTED. 🌸
  • subpixel_order β€” NOT YET DOCUMENTED. πŸ¦‹
  • width β€” NOT YET DOCUMENTED. ⭐
  • height β€” NOT YET DOCUMENTED. πŸ’œ
  • mwidth β€” NOT YET DOCUMENTED. 🌈
  • mheight β€” NOT YET DOCUMENTED. πŸ‘‘
ngl the docs here are lowkey just a row of "NOT YET DOCUMENTED." and honestly? we respect the transparency. if it's not written down, i'm not about to make it up. that's the rule, bestie. πŸŽ€

πŸ’… DESCRIPTION πŸ’…

...yeah there's nothing here. the section exists, the words do not. we move. πŸ’€


🌟 SEE ALSO 🌟

also empty, bestie. nothing to see. nothing to also. πŸ•³οΈβœ¨


πŸ‘‘ AUTHOR πŸ‘‘

Generated from randr.xml. if you spot something wrong and wanna fix it or make it better, hit up xcb@lists.freedesktop.org β€” that's the address for corrections and improvements. go off, fr fr πŸ’Œ


and that's the whole page!! πŸŽ‰ this little gem came from X Version 11, libxcb 1.17, and yes i know that footer line was doing the most with the truncation β€” xcb_randr_scre...notify_event_t(3) said what it said. anyway. slay, go handle your screen change notifications, and remember: not documented β‰  not real, it just means nobody wrote it down yet πŸ«ΆπŸ’–