xcb_dri2_inva...uffers_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

πŸ’… NAME

xcb_dri2_invalidate_buffers_event_t β€” bestie, the NAME section literally just says the name and nothing else, so that's the whole vibe. It's an XCB event datastructure from XCB Events, living its best life in libxcb 1.17.0 ✨


πŸ¦‹ SYNOPSIS

First things first, you gotta pull in the header:

#include <xcb/dri2.h>

πŸŽ€ Event datastructure

Here's the whole glow-up, exactly as it is:

typedef struct xcb_dri2_invalidate_buffers_event_t {
    uint8_t        response_type;
    uint8_t        pad0;
    uint16_t       sequence;
    xcb_drawable_t drawable;
} xcb_dri2_invalidate_buffers_event_t;

✨ EVENT FIELDS

  • response_type β€” the type of this event, and in this case it's XCB_DRI2_INVALIDATE_BUFFERS πŸ’– this field is also chillin' in the xcb_generic_event_t, which is literally how you tell events apart from each other. it's giving "hello, it's me" energy.
  • sequence β€” the sequence number of the last request processed by the X11 server 🫢 the receipts, fr fr.
  • drawable β€” NOT YET DOCUMENTED. yeah. that's it. that's the whole description. the mystery continues πŸ˜­πŸ’€

🌸 DESCRIPTION

absolutely nothing here. the section exists, the words do not. iconic silence, no cap πŸ™ˆβœ¨


🌈 SEE ALSO

nothing listed. nothing at all. an empty runway, and we're walking it πŸ’…


πŸ‘‘ AUTHOR

Generated from dri2.xml. Contact xcb@lists.freedesktop.org for corrections and improvements πŸ’œ


so yeah β€” this page came to you from X Version 11 and libxcb 1.17.0, and that's the whole thing, bestie. go forth and invalidate those buffers πŸ¦‹βœ¨πŸ’–