xcb_glx_get_floatv(3)

✨ xcb_glx_get_floatv ✨

okay bestie, welcome to the xcb_glx_get_floatv page from the XCB Requests crew 💅 this is one of those GLX request pages, and honestly? it's giving "short but mysterious". we're gonna go through it together, no cap.

---

🌸 NAME 🌸

xcb_glx_get_floatv — literally no description in the source, bestie. the manpage just left it blank, so that's what we're working with. iconic in a "the author said figure it out" way fr fr 🫶

---

🎀 SYNOPSIS 🎀

first up, the include, because everything starts with the include:

#include <xcb/glx.h>

💖 Request function 💖

xcb_glx_get_floatv_cookie_t xcb_glx_get_floatv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t pname);

🦋 Reply datastructure 🦋

here's the struct, and yes you read it right, there's padding, there's always padding, it's giving "structs need to be aligned and we respect that" ✨

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

🌈 Reply function 🌈

xcb_glx_get_floatv_reply_t
       *xcb_glx_get_floatv_reply(xcb_connection_t *conn,
       xcb_glx_get_floatv_cookie_t cookie, xcb_generic_error_t **e);

💜 Reply accessors 💜

these are your lil helpers for poking at the reply, bestie:

xcb_glx_float32_t *xcb_glx_get_floatv_data(const
       xcb_glx_get_floatv_request_t *reply);

int xcb_glx_get_floatv_data_length(const xcb_glx_get_floatv_reply_t
       *reply);

xcb_generic_iterator_t xcb_glx_get_floatv_data_end(const
       xcb_glx_get_floatv_reply_t *reply);

---

🍓 REQUEST ARGUMENTS 🍓

• conn — the XCB connection to X11. your lil phone line to the server, basically 📞
• context_tag — TODO: NOT YET DOCUMENTED. yeah. the manpage said "we'll get to it" and then never got to it 😭
• pname — TODO: NOT YET DOCUMENTED. same energy. also undocumented. we're all just vibing here 💀

---

⭐ REPLY FIELDS ⭐

• response_type — the type of this reply, which in this case is XCB_GLX_GET_FLOATV. this field is also chillin' inside xcb_generic_reply_t, and you can use it to tell replies apart from each other. it's the name tag at the party 🎀
• sequence — the sequence number of the last request processed by the X11 server. lowkey the receipt number of the conversation 🧾
• length — the length of the reply, in words. and reminder bestie: a word is 4 bytes. don't forget or the math will betray you 💅
• n — TODO: NOT YET DOCUMENTED. another mystery field, we love that for us 🙈
• datum — TODO: NOT YET DOCUMENTED. yes queen, also undocumented. the lore is simply missing 🔥

---

💀 DESCRIPTION 💀

nothing here. the DESCRIPTION section is empty. that's it. that's the section. we move 🦋

---

🌸 RETURN VALUE 🌸

it returns an xcb_glx_get_floatv_cookie_t. and here's the important part, bestie: errors have to be handled when you call the reply function xcb_glx_get_floatv_reply 👑

if you'd rather handle errors in the event loop instead, use xcb_glx_get_floatv_unchecked. see xcb-requests(3) for the deets. pick your fighter, both are valid 💖

---

😭 ERRORS 😭

this request does never generate any errors.

no error drama. none. zero. it's the chillest request in the group chat 🫶

---

🔥 SEE ALSO 🔥

empty. nothing linked. the SEE ALSO section said "no thoughts, head empty". 🧚

---

👑 AUTHOR 👑

generated from glx.xml. for corrections and improvements, hit up xcb@lists.freedesktop.org 📧 they're the ones who'd actually know what pname is, ngl.

---

and that's the whole page, bestie!! this was libxcb 1.17.0, from X Version 11, and the page itself is dated the same era, brought to you by the XCB Requests girlies. slay, stay padded (the structs are), and go read xcb-requests(3) if you haven't 💅✨💖