xcb_no_exposure_event_t(3)
π xcb_no_exposure_event_t(3) π
okay so bestie, welcome to the XCB Events corner of the manual π
this one's about xcb_no_exposure_event_t, and ngl the manpage itself is a lil bit of a mystery box β the NAME line is literally just a dash, no description, no nothing. iconic of it, honestly.
β¨ NAME β¨
xcb_no_exposure_event_t β that's it. that's the name. the original page gives us a lonely little dash here and we're not gonna invent lore that isn't there, bestie. π«Ά
πΈ SYNOPSIS πΈ
#include <xcb/xproto.h>
π Event datastructure π
typedef struct xcb_no_exposure_event_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
xcb_drawable_t drawable;
uint16_t minor_opcode;
uint8_t major_opcode;
uint8_t pad1;
} xcb_no_exposure_event_t;
look at that struct, it's giving very structured, very demure π copy it exactly if you're typing it out, character for character, no cap.
π¦ EVENT FIELDS π¦
response_typeβ the vibe check field π this is the type of the event, and in this case it'sXCB_NO_EXPOSURE. it also lives inxcb_generic_event_t, so you can use it to tell events apart from each other. very main character of it.sequenceβ the sequence number of the last request processed by the X11 server. so like, the receipts of what the server just handled. π§Ύdrawableβ NOT YET DOCUMENTED. π« fr fr, that's literally all the original says. no notes, no lore, just mystery.minor_opcodeβ NOT YET DOCUMENTED. π again. the docs simply did not show up to class.major_opcodeβ NOT YET DOCUMENTED. π third one. we love a consistently undocumented trio, periodt.
π DESCRIPTION π
this section is empty in the original. like, fully empty. nothing. the void. and we're not about to make stuff up, because that would be a fake fact and fake facts are not the move, bestie. π
β SEE ALSO β
also empty, bestie. nothing here to point you at. if you were hoping for a little cross-reference momentβ¦ it's not coming. π
π AUTHOR π
Generated from xproto.xml. If you spot something wrong or wanna suggest improvements, contact xcb@lists.freedesktop.org β they're the ones who can actually fix it. π«Ά
lowkey important reminder: a bunch of these fields are literally marked NOT YET DOCUMENTED. in the source, so don't go assuming behaviour that isn't written down. that's a guess, and guesses are not facts. π
okay that's the whole page, bestie β shoutout to X Version 11 and libxcb 1.17.0 for bringing us this absolute enigma of an event struct. slay, stay documented, mwah πβ¨π¦
π¦ 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