xcb_glx_get_queryiv_arb(3)

💖 xcb_glx_get_queryiv_arb — bestie edition 💖

okay so this one is from the XCB Requests corner of the world, and the page is literally called xcb_glx_get_queryiv_arb(3). She's a GLX request, she's got a cookie, she's got a reply, and honestly? She's giving "quiet but useful." Let's get into it 🫶

---

✨ NAME ✨

xcb_glx_get_queryiv_arb — (yeah bestie, the original page leaves the description blank here. Not me making stuff up. We keep it real 💀)

---

🌸 SYNOPSIS 🌸

First things first, the include. Don't forget her:

#include <xcb/glx.h>

💅 Request function

xcb_glx_get_queryiv_arb_cookie_t
       xcb_glx_get_queryiv_arb(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t target,
       uint32_t pname);

🎀 Reply datastructure

Look at this struct, she's structured, she's organized, she's iconic:

typedef struct xcb_glx_get_queryiv_arb_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad1[4];
    uint32_t n;
    int32_t  datum;
    uint8_t  pad2[12];
} xcb_glx_get_queryiv_arb_reply_t;

🦋 Reply function

xcb_glx_get_queryiv_arb_reply_t
       *xcb_glx_get_queryiv_arb_reply(xcb_connection_t *conn,
       xcb_glx_get_queryiv_arb_cookie_t cookie,
       xcb_generic_error_t **e);

🌈 Reply accessors

These are the little helpers that go through the reply for you, no cap:

int32_t *xcb_glx_get_queryiv_arb_data(const
       xcb_glx_get_queryiv_arb_request_t *reply);

int xcb_glx_get_queryiv_arb_data_length(const
       xcb_glx_get_queryiv_arb_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_queryiv_arb_data_end(const
       xcb_glx_get_queryiv_arb_reply_t *reply);

---

🌟 REQUEST ARGUMENTS 🌟

• conn — your XCB connection to X11. The main character, fr fr.
• context_tag — TODO: NOT YET DOCUMENTED. Like, the docs just didn't show up. Not my fault bestie 😭
• target — TODO: NOT YET DOCUMENTED. Same situation.
• pname — TODO: NOT YET DOCUMENTED. Also a mystery. The mystery continues ✨

---

💜 REPLY FIELDS 💜

• response_type — what kind of reply this even is. In this case it's XCB_GLX_GET_QUERYIV_ARB. This field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other — a little vibe check for your packets 👑
• sequence — the sequence number of the last request the X11 server actually processed. Tracking numbers, but make it X11.
• length — how long the reply is, measured in words. And a word here is 4 bytes, so don't get it twisted 💅
• n — TODO: NOT YET DOCUMENTED. 🫠
• datum — TODO: NOT YET DOCUMENTED. 🫠

---

🍓 DESCRIPTION 🍓

(Yes bestie, this section is empty in the original. There is literally nothing here. Enjoy the silence. It's giving minimalism. 💀)

---

⭐ RETURN VALUE ⭐

You get back an xcb_glx_get_queryiv_arb_cookie_t. Cute, right? But here's the thing — errors have to be handled when you call the reply function xcb_glx_get_queryiv_arb_reply. So don't just grab the cookie and ghost her, okay?

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

---

🔥 ERRORS 🔥

This request does never generate any errors. Zero. None. A flawless queen with no drama. Periodt. 👑

---

🧚 SEE ALSO 🧚

(Also empty in the original! Nothing to link, bestie. We love a low-maintenance page 🌸)

---

🌸 AUTHOR 🌸

Generated from glx.xml. If something looks off and you want to send corrections and improvements, hit up xcb@lists.freedesktop.org — they're taking notes, and they're literally asking for your feedback 💌

---

okay that's the whole page, we did it, and it's from X Version 11, shipped with libxcb 1.17.0, page xcb_glx_get_queryiv_arb(3) — mwah, slay, go read your headers, love u bye 🎀✨💖