xcb_glx_is_direct(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_is_direct(3) ✨

okay bestie, so this is the manual page for xcb_glx_is_direct from the XCB Requests crew 💅 it lives in section 3, it's part of the XCB GLX family, and it's here to answer one very specific little question for you. let's get into it 🫶

🌸 NAME 🌸

xcb_glx_is_direct — (the original page leaves this blank, so like... the name is the name, iykyk 😭)

🦋 SYNOPSIS 🦋

First, you gotta bring in the header:

#include <xcb/glx.h>

✨ Request function ✨

xcb_glx_is_direct_cookie_t xcb_glx_is_direct(xcb_connection_t *conn,
       xcb_glx_context_t context);

🎀 Reply datastructure 🎀

typedef struct xcb_glx_is_direct_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  is_direct;
    uint8_t  pad1[23];
} xcb_glx_is_direct_reply_t;

💖 Reply function 💖

xcb_glx_is_direct_reply_t
       *xcb_glx_is_direct_reply(xcb_connection_t *conn,
       xcb_glx_is_direct_cookie_t cookie, xcb_generic_error_t **e);

🔥 REQUEST ARGUMENTS 🔥

  • conn — the XCB connection to X11, your little hotline to the server 📞
  • context — TODO: NOT YET DOCUMENTED. yeah babe, they just never wrote it 🙈

💜 REPLY FIELDS 💜

  • response_type — what kind of reply this is. In this case it's XCB_GLX_IS_DIRECT. Fun fact: this field also shows up in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other 👑
  • sequence — the sequence number of the last request the X11 server actually processed. it's giving receipt number 🧾
  • length — how long the reply is, measured in words (and a word here = 4 bytes, periodt) ⭐
  • is_direct — TODO: NOT YET DOCUMENTED. the mystery continues 😭

🌈 DESCRIPTION 🌈

(yeah... the original page just leaves this one empty. not me noticing that 💀)

✨ RETURN VALUE ✨

It hands you back an xcb_glx_is_direct_cookie_t 🍪 and here's the tea: errors have to be handled when you call the reply function xcb_glx_is_direct_reply.

But if you'd rather handle your errors in the event loop instead, use xcb_glx_is_direct_unchecked — and check out xcb-requests(3) for all the details on that whole situation 🫶

💅 ERRORS 💅

Good news bestie: this request never generates any errors. not a single one. flawless behavior, honestly 🎀

👑 SEE ALSO 👑

(the original page lists nothing here — nothing to see, literally 😭)

🦋 AUTHOR 🦋

Generated from glx.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they want your feedback fr fr 💌

okay that's the whole page!! 💖 this lil writeup came to you courtesy of X Version 11 and libxcb 1.17.0, so go forth and check if your GLX context is direct, queen 👑✨

📦 where this page comes from