xcb_randr_notify_event_t(3)
π xcb_randr_notify_event_t(3) π
okay bestie, so this is a page from the XCB Events manual β that's the XCB Events section, if you're out here collecting manpages like PokΓ©mon π
β and it's all about a lil event datastructure called xcb_randr_notify_event_t. Buckle up π
β¨ NAME β¨
xcb_randr_notify_event_t β
and that's... it. that's the whole NAME section. no description. it's giving mysterious main character energy. we move π
πΈ SYNOPSIS πΈ
#include <xcb/randr.h>
π¦ Event datastructure π¦
typedef struct xcb_randr_notify_event_t {
uint8_t response_type;
uint8_t subCode;
uint16_t sequence;
xcb_randr_notify_data_t u;
} xcb_randr_notify_event_t;
look at her. four fields, one union, absolutely iconic π
π EVENT FIELDS π
response_typeβ the type of this event, and in this particular case it'sXCB_RANDR_NOTIFY. plot twist: this field is also chillin' in thexcb_generic_event_t, so you can use it to tell your events apart from each other. it's literally the "which one of y'all is this" field, no cap.sequenceβ the sequence number of the last request that the X11 server processed. yes, the last one. that's the one. π«ΆsubCodeβ NOT YET DOCUMENTED. ngl, she's keeping secrets. πuβ NOT YET DOCUMENTED. also secretive. also mysterious. we love a cryptic queen π
π DESCRIPTION π
ok so this section is empty. like, genuinely empty. nothing here. the manpage said "DESCRIPTION" and then said nothing else. not me being handed a blank page and still writing an entire group chat message about it π
π SEE ALSO π
also empty!! no references, no cross-links, no "go read this next." you're on your own bestie, but honestly? you got this. i believe in you π
π AUTHOR π
generated from randr.xml. and if you spot something wrong or wanna suggest improvements, hit up xcb@lists.freedesktop.org β they're the ones to talk to, fr fr. corrections and improvements welcome, so don't be shy π«Ά
and that's the whole vibe check, bestie β¨ this page came to you straight outta X Version 11, riding with libxcb 1.17.0, and its official government name is xcb_randr_notify_event_t(3). slay, drink water, and may your response_type always be exactly what you expected ππΈπ¦ periodt.
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms