xcb_glx_get_integerv(3)

💅 xcb_glx_get_integerv(3) — XCB Requests, bestie edition ✨

okay so. welcome to the group chat, this is xcb_glx_get_integerv from the XCB request fam, and yes it lives in section 3 of your manual, and yes I'm gonna walk you through every single crumb of it. 🍓

---

🌸 NAME 🌸

xcb_glx_get_integerv —

not gonna lie, the original literally just has a dash here with nothing after it. the NAME section is giving mystery. 🫶 we move.

---

🦋 SYNOPSIS 🦋

first things first, you gotta bring in the header, no cap:

#include <xcb/glx.h>

✨ Request function ✨

xcb_glx_get_integerv_cookie_t
       xcb_glx_get_integerv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t pname);

that's the one you call, she hands you back a cookie, we love a cookie. 🍪

🎀 Reply datastructure 🎀

here's the whole reply struct, every field, exactly as written, no edits, periodt:

typedef struct xcb_glx_get_integerv_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_integerv_reply_t;

💖 Reply function 💖

xcb_glx_get_integerv_reply_t
       *xcb_glx_get_integerv_reply(xcb_connection_t *conn,
       xcb_glx_get_integerv_cookie_t cookie, xcb_generic_error_t **e);

🌈 Reply accessors 🌈

the lil helpers that go digging inside the reply for you:

int32_t *xcb_glx_get_integerv_data(const xcb_glx_get_integerv_request_t
       *reply);

int xcb_glx_get_integerv_data_length(const xcb_glx_get_integerv_reply_t
       *reply);

xcb_generic_iterator_t xcb_glx_get_integerv_data_end(const
       xcb_glx_get_integerv_reply_t *reply);

⚠️ yes, xcb_glx_get_integerv_data takes an xcb_glx_get_integerv_request_t * while the other two take the reply type. that's literally what the manual says, so that's literally what you get. don't come for me, I'm just the messenger 💀

---

👑 REQUEST ARGUMENTS 👑

• conn — the XCB connection to X11. your lil hotline to the server, iconic.
• context_tag — TODO: NOT YET DOCUMENTED. bestie the docs simply did not show up. 🙈
• pname — TODO: NOT YET DOCUMENTED. same vibe, same empty plate. 😭

---

💜 REPLY FIELDS 💜

• response_type — the type of this reply, and in this case it's XCB_GLX_GET_INTEGERV. this field is also chillin' in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. main character identification energy. 👑
• sequence — the sequence number of the last request processed by the X11 server.
• length — the length of the reply, in words (and a word is 4 bytes, fyi, iykyk).
• n — TODO: NOT YET DOCUMENTED. 🫠
• datum — TODO: NOT YET DOCUMENTED. 🫠

---

✨ DESCRIPTION ✨

okay so this section is, and I cannot stress this enough, completely empty in the original. nothing. a void. a vibe check that returned zero results. 🌌

---

🫶 RETURN VALUE 🫶

you get back an xcb_glx_get_integerv_cookie_t. errors? you gotta handle those yourself when you call the reply function xcb_glx_get_integerv_reply. that's the deal, fr fr.

and if you'd rather handle errors in the event loop instead, use xcb_glx_get_integerv_unchecked. peek xcb-requests(3) for the deets. 💅

---

💀 ERRORS 💀

this request does never generate any errors. not one. zero. she's unproblematic, she's chill, she's lowkey perfect. 🌸

---

🔥 SEE ALSO 🔥

yeah... this one's empty too. no cross-references, no links, no crumbs. the SEE ALSO section is standing there in silence. 😶🌫️

---

🌟 AUTHOR 🌟

Generated from glx.xml. got corrections or improvements? contact xcb@lists.freedesktop.org and they'll sort you out. 📧

---

and that's the whole page, bestie!! 💖

signing off from X Version 11, rocking libxcb 1.17.0, on the xcb_glx_get_integerv(3) manual page — stay glxy, stay hydrated, and remember: the TODO sections are not your fault. 🧚✨🎀🦋