XCB_GLX_PBUFFER_CLOBBER_EVENT_T(3)
π xcb_glx_pbuffer_clobber_event_t β the manual page, bestie edition
okay so you opened xcb_glx_pbuffer_clobber_event_t(3) from the XCB Events crew and the NAME section is literally just the name and nothing else, which is giving mysterious. that's fine, we're gonna unpack the whole thing together, no cap. π
β¨ NAME β¨
xcb_glx_pbuffer_clobber_event_t β and that's it, that's the whole name section, she's lowkey just standing there. π
πΈ SYNOPSIS πΈ
first things first, you gotta bring in the header, bestie:
#include <xcb/glx.h>
π¦ Event datastructure
here's the whole struct, character for character, don't touch a single semicolon:
typedef struct xcb_glx_pbuffer_clobber_event_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint16_t event_type;
uint16_t draw_type;
xcb_glx_drawable_t drawable;
uint32_t b_mask;
uint16_t aux_buffer;
uint16_t x;
uint16_t y;
uint16_t width;
uint16_t height;
uint16_t count;
uint8_t pad1[4];
} xcb_glx_pbuffer_clobber_event_t;
it's giving "a bunch of fields and two little padding arrays holding it together." iconic honestly. π
π₯ EVENT FIELDS π₯
let's go field by field, i got you:
response_typeβ the type of this event, and in this case it'sXCB_GLX_PBUFFER_CLOBBER. plot twist: this field also lives insidexcb_generic_event_t, so you can use it to tell your events apart from each other. very main character of it. βsequenceβ the sequence number of the last request processed by the X11 server. that's the tea. πevent_typeβNOT YET DOCUMENTED.yeah bestie, she said nothing. πdraw_typeβNOT YET DOCUMENTED.also silent. πdrawableβNOT YET DOCUMENTED.still not talking. πb_maskβNOT YET DOCUMENTED.we know nothing. π«Άaux_bufferβNOT YET DOCUMENTED.mystery queen. πxβNOT YET DOCUMENTED.β¨yβNOT YET DOCUMENTED.β¨widthβNOT YET DOCUMENTED.β¨heightβNOT YET DOCUMENTED.β¨countβNOT YET DOCUMENTED.and that's the last one, we ran out of lore. π
real talk: a whole bunch of these fields are officially NOT YET DOCUMENTED, so please don't go inventing behaviour for them. i'm not guessing, and neither should you. π
π§ DESCRIPTION π§
the DESCRIPTION section is empty. like, fully empty. it's giving "no thoughts, head empty, just vibes." so there's genuinely nothing to summarise here β the fields above and the struct are the whole story. π
π SEE ALSO π
also empty, bestie. no cross-references, no friends, no nothing. she's a solo act. π
π AUTHOR π
generated from glx.xml. if you spot something that needs correcting or improving, hit up xcb@lists.freedesktop.org. that's the whole plug. π«Ά
and that's the page!! go forth and clobber some pbuffers, or at least tell your events apart with response_type, periodt. πβ¨
X Version 11 Β· libxcb 1.17 Β· xcb_glx_pbuffer_clobber_event_t(3) β mwah, love u, bye bestie ππ¦
π¦ 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