XCB_GLX_PBUFFER_CLOBBER_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_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's XCB_GLX_PBUFFER_CLOBBER. plot twist: this field also lives inside xcb_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 πŸŽ€πŸ¦‹