xcb_glx_make_current(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_glx_make_current(3) 💖

okay bestie, welcome to the XCB Requests corner of the manual, and today's main character is xcb_glx_make_current. she's a GLX request from <xcb/glx.h> and she's here to, well, make something current. iconic behaviour, honestly. 🌈

✨ NAME ✨

xcb_glx_make_current — and that's it, that's the whole description. the manpage literally left this one blank, bestie. no cap. the description field is just… vibes. empty vibes. 💀

✨ SYNOPSIS ✨

#include <xcb/glx.h>

🎀 Request function

xcb_glx_make_current_cookie_t
       xcb_glx_make_current(xcb_connection_t *conn,
       xcb_glx_drawable_t drawable, xcb_glx_context_t context,
       xcb_glx_context_tag_t old_context_tag);

🦋 Reply datastructure

typedef struct xcb_glx_make_current_reply_t {
    uint8_t               response_type;
    uint8_t               pad0;
    uint16_t              sequence;
    uint32_t              length;
    xcb_glx_context_tag_t context_tag;
    uint8_t               pad1[20];
} xcb_glx_make_current_reply_t;

🌸 Reply function

xcb_glx_make_current_reply_t
       *xcb_glx_make_current_reply(xcb_connection_t *conn,
       xcb_glx_make_current_cookie_t cookie, xcb_generic_error_t **e);

✨ REQUEST ARGUMENTS ✨

  • conn — your XCB connection to X11. the whole lil telephone line to the server, periodt. ☎️
  • drawable — TODO: NOT YET DOCUMENTED. yeah. the docs said "we'll get to it" and then did not get to it. 🙈
  • context — TODO: NOT YET DOCUMENTED. same energy, same blankness. 😭
  • old_context_tag — TODO: NOT YET DOCUMENTED. the trilogy of mystery. three args, zero explanations, we love a cryptic queen. 👑

✨ REPLY FIELDS ✨

  • response_type — what kind of reply this is, and in this specific case it's XCB_GLX_MAKE_CURRENT. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other — like name tags at a party but for protocol messages. 🎉
  • sequence — the sequence number of the last request the X11 server got around to processing. it's the server's lil "I did this one" receipt. 🧾
  • length — how long the reply is, measured in words. and bestie, a word is 4 bytes, don't forget it. 📏
  • context_tag — TODO: NOT YET DOCUMENTED. the mystery continues. she's giving enigma. 💅

✨ DESCRIPTION ✨

…nothing. literally nothing. the DESCRIPTION section is empty. the author said "no thoughts, head empty" and hit publish. not me reading an empty section like 👁️👄👁️

✨ RETURN VALUE ✨

she hands you back an xcb_glx_make_current_cookie_t 🍪. errors? those don't show up here — you have to deal with them when you call the reply function xcb_glx_make_current_reply.

but wait, there's another option: if you'd rather catch errors in your event loop instead, use xcb_glx_make_current_unchecked. peek xcb-requests(3) for the whole rundown on how that works. 🫶

✨ ERRORS ✨

this request does never generate any errors. not one. zero. she's flawless, she's unbothered, she's error-free. ✨

✨ SEE ALSO ✨

…also empty. the manpage really said "go find it yourself bestie". 💀

✨ AUTHOR ✨

generated from glx.xml. if you spot something wrong or wanna suggest improvements, hit up xcb@lists.freedesktop.org — they're the ones who can fix it up. 📬

and that's the whole page, bestie!! this lil gem ships with X Version 11 and libxcb 1.17.0. mwah, go forth and make things current. 💅✨🎀🦋💖

📦 where this page comes from