XCB_GLX_GET_TEX_LEVEL_PARAMETERFV_UNCHECKED(3)

💖 NAME 💖

xcb_glx_get_tex_level_parameterfv — bestie, it's a GLX request from libxcb that asks the X server for texture level parameters as floats. The original page leaves the description blank, so we're keeping it blank, no cap. 🫶

---

✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/glx.h>

🧚 Request function

xcb_glx_get_tex_level_parameterfv_cookie_t
       xcb_glx_get_tex_level_parameterfv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t target,
       int32_t level, uint32_t pname);

🎀 Reply datastructure

okay so this is the struct the reply lands in, look at her:

typedef struct xcb_glx_get_tex_level_parameterfv_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_tex_level_parameterfv_reply_t;

💅 Reply function

xcb_glx_get_tex_level_parameterfv_reply_t
       *xcb_glx_get_tex_level_parameterfv_reply(xcb_connection_t *conn,
       xcb_glx_get_tex_level_parameterfv_cookie_t cookie,
       xcb_generic_error_t **e);

🌸 Reply accessors

these lil helpers get the data out for you, slay:

xcb_glx_float32_t *xcb_glx_get_tex_level_parameterfv_data(const
       xcb_glx_get_tex_level_parameterfv_request_t *reply);

int xcb_glx_get_tex_level_parameterfv_data_length(const
       xcb_glx_get_tex_level_parameterfv_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_tex_level_parameterfv_data_end(const
       xcb_glx_get_tex_level_parameterfv_reply_t *reply);

👀 yes bestie, the _data accessor really does take a const xcb_glx_get_tex_level_parameterfv_request_t *reply. That's what the page says. We're keeping it exactly like that. Not my business, not my problem. 💀

---

🌈 REQUEST ARGUMENTS 🌈

• conn — your XCB connection to X11. the whole reason we're here fr fr.
• context_tag — TODO: NOT YET DOCUMENTED. (the docs said "later" and later never came 😭)
• target — TODO: NOT YET DOCUMENTED.
• level — TODO: NOT YET DOCUMENTED.
• pname — TODO: NOT YET DOCUMENTED.

---

🦋 REPLY FIELDS 🦋

• response_type — the type of this reply, and in this case it's XCB_GLX_GET_TEX_LEVEL_PARAMETERFV. plot twist: this field is also chilling inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other. iconic.
• sequence — the sequence number of the last request the X11 server processed. lowkey just a receipt number.
• length — how long the reply is, in words. and a word is 4 bytes, in case you forgot. 🫶
• n — TODO: NOT YET DOCUMENTED.
• datum — TODO: NOT YET DOCUMENTED.

---

💜 DESCRIPTION 💜

...and that's it. that's the section. it's empty in the original, so it's empty here. the vibes are immaculate but the words are zero. 🎀

---

⭐ RETURN VALUE ⭐

It hands you back an xcb_glx_get_tex_level_parameterfv_cookie_t. Cookies are cute but they're not the answer — you have to handle errors when you call the reply function xcb_glx_get_tex_level_parameterfv_reply. That's the moment of truth.

If you'd rather catch your errors in the event loop instead (main character energy tbh), use xcb_glx_get_tex_level_parameterfv_unchecked. More on that in xcb-requests(3). 💅

---

🔥 ERRORS 🔥

This request does never generate any errors. literally zero. not one. flawless behaviour, we love to see it. ✨

---

💀 SEE ALSO 💀

(blank in the original, blank here — nothing to link, nothing to see, no notes.)

---

🌸 AUTHOR 🌸

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

---

and that's the whole page bestie!! this one came from X Version 11, libxcb 1.17.0, and yeah the title got chopped in the header like xcb_glx_get_t...el_parameterfv(3) because even manpages run out of room sometimes. bye ily, go read your replies responsibly 🫶💖✨