xcb_glx_is_enabled(3)

🎀 NAME 🎀

xcb_glx_is_enabled — and that's it bestie, that's the whole name line. The original literally leaves the description slot blank (it's just xcb_glx_is_enabled - with nothing after the dash), so we're not gonna make stuff up. It lives in the XCB Requests manual as page xcb_glx_is_enabled(3). 💅

---

✨ SYNOPSIS ✨

#include <xcb/glx.h>

🦋 Request function 🦋

xcb_glx_is_enabled_cookie_t xcb_glx_is_enabled(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t capability);

💖 Reply datastructure 💖

typedef struct xcb_glx_is_enabled_reply_t {
    uint8_t          response_type;
    uint8_t          pad0;
    uint16_t         sequence;
    uint32_t         length;
    xcb_glx_bool32_t ret_val;
} xcb_glx_is_enabled_reply_t;

🌸 Reply function 🌸

xcb_glx_is_enabled_reply_t
       *xcb_glx_is_enabled_reply(xcb_connection_t *conn,
       xcb_glx_is_enabled_cookie_t cookie, xcb_generic_error_t **e);

---

🫶 REQUEST ARGUMENTS 🫶

• conn — your XCB connection to X11, aka the group chat with the server. 💌
• context_tag — TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "we'll fill this in later" and then never did 😭
• capability — also TODO: NOT YET DOCUMENTED. the mystery continues 🙈

---

👑 REPLY FIELDS 👑

• response_type — what kind of reply this is; for this one it's XCB_GLX_IS_ENABLED. It 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. 🧚
• length — how long the reply is, measured in words (and a word is 4 bytes, keep up 💅).
• ret_val — TODO: NOT YET DOCUMENTED. once again the void stares back 💀

---

🌈 DESCRIPTION 🌈

So… there is a DESCRIPTION heading in the original and it's completely empty. Nothing. A ghost town. No text at all, so there's nothing for me to spill — I'm not gonna invent lore that isn't there. 🕳️

---

⭐ RETURN VALUE ⭐

Returns an xcb_glx_is_enabled_cookie_t. Errors have to be handled when you call the reply function xcb_glx_is_enabled_reply. 🍪

If you'd rather handle errors in the event loop instead, use xcb_glx_is_enabled_unchecked. See xcb-requests(3) for the details. 📚

---

💀 ERRORS 💀

Good news for once: this request does never generate any errors. Iconic behaviour, honestly. 👑

---

🔥 SEE ALSO 🔥

The original has this heading and then… nothing under it. No references, no pages, nada. Consider yourself seen. 🫥

---

💜 AUTHOR 💜

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 🌸

---

okay that's the whole page, mwah 💖 This was X Version 11, shipped as libxcb 1.17.0 — go forth and check your capabilities, bestie, and remember: a word is 4 bytes and you are doing amazing sweetie 🎀✨🦋