xcb_xf86dri_create_drawable(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_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's XCB_XF86DRI_CREATE_DRAWABLE. This field also lives inside xcb_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. πŸ‘‘πŸ’–