xcb_dbe_allocate_back_buffer(3)
β¨ xcb_dbe_allocate_back_buffer β¨
okay bestie, welcome to the XCB Requests section of the manual, and today's main character is xcb_dbe_allocate_back_buffer β the lil' function that allocates a back buffer. yes, that's literally its whole job. no cap. π
π¦ NAME π¦
xcb_dbe_allocate_back_buffer β Allocates a back buffer π
πΈ SYNOPSIS πΈ
#include <xcb/dbe.h>
β¨ Request function β¨
xcb_void_cookie_t xcb_dbe_allocate_back_buffer(xcb_connection_t *conn,
xcb_window_t window, xcb_dbe_back_buffer_t buffer,
uint8_t swap_action);
π REQUEST ARGUMENTS π
connβ your XCB connection to X11. the whole link to the X server, the group chat you're sending this request through π«Άwindowβ the window you wanna add the back buffer to. that's the vibe.bufferβ the buffer id you're associating with the back buffer. give it a name tag, bestie π·οΈswap_actionβ the swap action most likely to be used to present this back buffer. and listen β this is only a hint. it does not preclude you from using other swap actions later, so don't stress, it's not a binding contract or anything π
π DESCRIPTION π
so what's actually happening here? it associates buffer with the back buffer of window. and here's the cute part: multiple ids may be associated with the back buffer β the back buffer itself is created by the first allocate call and destroyed by the last deallocate. first one in builds the club, last one out turns off the lights. it's giving β¨shared custodyβ¨, fr fr.
π RETURN VALUE π
it returns an xcb_void_cookie_t. and if there are any errors? bestie, you gotta handle those in the event loop. that's the deal.
but wait β if you'd rather handle errors directly with xcb_request_check instead, then use xcb_dbe_allocate_back_buffer_checked. different function, same energy. see xcb-requests(3) for the deets. π
π ERRORS π
this request does never generate any errors.
iconic. flawless. zero drama. it simply does not miss. π
π SEE ALSO π
xcb-requests(3)π¦
β AUTHOR β
Generated from dbe.xml. if you got corrections or improvements, hmu at xcb@lists.freedesktop.org β they're literally asking for it, so slide into their inbox π¬
X Version 11 β¦ libxcb 1.17.0 β¦ xcb_dbe_allocate_back_buffer(3)
and that's the whole page, bestie π«Ά go allocate that back buffer, slay, and remember: first allocate creates it, last deallocate destroys it. periodt. πβ¨ππ¦πΈ
π¦ 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