XCB_DBE_DEALLOCATE_BACK_BUFFER_CHECKED(3)

πŸ’– xcb_dbe_deallocate_back_buffer β€” from the XCB Requests manual (section 3) ✨

okay bestie, listen, we're doing some X11 double-buffering cleanup today and honestly? it's giving "tidying my room at 2am" energy but for back buffers πŸŽ€


🌸 NAME 🌸

xcb_dbe_deallocate_back_buffer β€” deallocates a back buffer πŸ’…


✨ SYNOPSIS ✨

#include <xcb/dbe.h>

πŸ¦‹ Request function πŸ¦‹

xcb_void_cookie_t xcb_dbe_deallocate_back_buffer(xcb_connection_t *conn,
       xcb_dbe_back_buffer_t buffer);

πŸ’œ REQUEST ARGUMENTS πŸ’œ

  • conn β€” your XCB connection to X11, aka your little hotline to the server, periodt πŸ”₯
  • buffer β€” the back buffer you want to deallocate. bye babe 🫢

🌈 DESCRIPTION 🌈

So basically, this deallocates the given buffer. that's the whole vibe.

but WAIT, there's lore πŸ‘€ β€” if buffer is an invalid id, a BadBuffer error is returned. and here's the part that matters most: because a window may have allocated multiple back buffer ids, the back buffer itself is not deleted until all these ids are deallocated by this call. it's not a "one and done" situation, it's a "wait for everyone to leave the group chat" situation πŸ’€


πŸ‘‘ RETURN VALUE πŸ‘‘

Returns an xcb_void_cookie_t. any errors (if any) have to be handled in the event loop, so don't come crying to the return value, she doesn't do that πŸ’…

if you'd rather handle errors directly with xcb_request_check instead, use xcb_dbe_deallocate_back_buffer_checked. see xcb-requests(3) for the details, iykyk πŸ“–


πŸŽ€ ERRORS πŸŽ€

this request does never generate any errors. clean. flawless. no drama. ate. ✨


πŸ”₯ SEE ALSO πŸ”₯


🌟 AUTHOR 🌟

Generated from dbe.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β€” they're literally the ones who'd know 🫢


ngl, that's the whole page bestie. go free those buffer ids. no cap. πŸ¦‹

and that's a wrap on X Version 11, libxcb 1.17.0 β€” stay iconic, xoxo πŸ’–πŸ‘‘