xcb_xf86dri_create_drawable(3)
π xcb_xf86dri_create_drawable(3) π
okay bestie, so this is a page from the XCB Requests manual, section 3 (that's the library-functions girlies π
). It's xcb_xf86dri_create_drawable, and it's genuinely so niche but we're gonna understand it together, fr fr.
β¨ NAME β¨
xcb_xf86dri_create_drawable β and that's it. No description. The original justβ¦ leaves it blank. Not me being lazy, the manpage literally has nothing there. Iconic of it, honestly. π«Ά
πΈ SYNOPSIS πΈ
π Request function
#include <xcb/xf86dri.h>
xcb_xf86dri_create_drawable_cookie_t
xcb_xf86dri_create_drawable(xcb_connection_t *conn,
uint32_t screen, uint32_t drawable);
π¦ Reply datastructure
typedef struct xcb_xf86dri_create_drawable_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t hw_drawable_handle;
} xcb_xf86dri_create_drawable_reply_t;
β Reply function
xcb_xf86dri_create_drawable_reply_t
*xcb_xf86dri_create_drawable_reply(xcb_connection_t *conn,
xcb_xf86dri_create_drawable_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ your XCB connection to X11. the whole main character of every request, lowkey.screenβ TODO: NOT YET DOCUMENTED. yeah. the manpage said what it said. πdrawableβ TODO: NOT YET DOCUMENTED. also a mystery. we move. π
π REPLY FIELDS π
response_typeβ the type of this reply, and in this specific case it'sXCB_XF86DRI_CREATE_DRAWABLE. This field also lives insidexcb_generic_reply_t, so you can use it to tell replies apart from each other. it's giving "name tag at a party" πsequenceβ the sequence number of the last request processed by the X11 server. chronological queen. πlengthβ how long the reply is, measured in words (and a word is 4 bytes, no cap).hw_drawable_handleβ TODO: NOT YET DOCUMENTED. she's undocumented and she's thriving. β¨
π§ DESCRIPTION π§
Nothing here, bestie. The original DESCRIPTION section is completely empty β it's giving "showed up to class and the professor never arrived". We simply vibe with the mystery. π¦
π RETURN VALUE π
Returns an xcb_xf86dri_create_drawable_cookie_t. Cookies are cute, but errors are not β and you have to handle them when you call the reply function, xcb_xf86dri_create_drawable_reply.
If you'd rather handle your errors inside the event loop instead, use xcb_xf86dri_create_drawable_unchecked. See xcb-requests(3) for the full tea. β
π ERRORS π
This request does never generate any errors. not one. zero. clean slate, flawless, no drama. π
πΈ SEE ALSO πΈ
Empty. Truly nothing listed. The original left this section a blank canvas and we respect the artistic choice. π¨
π«Ά AUTHOR π«Ά
Generated from xf86dri.xml. Wanna send corrections or improvements? Contact xcb@lists.freedesktop.org. They're literally waiting for your email bestie, go say hi. π
and that's the whole page, no notes β¨
this little legend came to you courtesy of X Version 11, libxcb 1.17.0, and yes β xcb_xf86dri_create_drawable(3) β slay, 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