xcb_glx_get_tex_envfv(3)

💖 xcb_glx_get_tex_envfv 💖

okay bestie so this one lives in section 3 of the manual — xcb_glx_get_tex_envfv(3) — and it's part of the XCB Requests family, which is literally the whole X11 request squad. grab a snack, we're doing GLX 💅

---

✨ NAME ✨

xcb_glx_get_tex_envfv -

not me pointing out that the NAME section is literally just the function name and a dash with nothing after it 😭 the original says what it says, and it says nothing. iconic behaviour honestly. moving on 🎀

---

✨ SYNOPSIS ✨

First up, you gotta bring the header in. like, obviously:

#include <xcb/glx.h>

🌸 Request function 🌸

xcb_glx_get_tex_envfv_cookie_t
       xcb_glx_get_tex_envfv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t target,
       uint32_t pname);

🦋 Reply datastructure 🦋

okay so this is the struct you get back. look at her:

typedef struct xcb_glx_get_tex_envfv_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_envfv_reply_t;

🧚 Reply function 🧚

xcb_glx_get_tex_envfv_reply_t
       *xcb_glx_get_tex_envfv_reply(xcb_connection_t *conn,
       xcb_glx_get_tex_envfv_cookie_t cookie, xcb_generic_error_t **e);

💜 Reply accessors 💜

these are your little helpers for digging through the reply, slay:

xcb_glx_float32_t *xcb_glx_get_tex_envfv_data(const
       xcb_glx_get_tex_envfv_request_t *reply);

int xcb_glx_get_tex_envfv_data_length(const
       xcb_glx_get_tex_envfv_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_tex_envfv_data_end(const
       xcb_glx_get_tex_envfv_reply_t *reply);

---

✨ REQUEST ARGUMENTS ✨

• conn — your XCB connection to X11. the whole line to the server, bestie 🔌
• context_tag — TODO: NOT YET DOCUMENTED. yeah... the docs said "figure it out yourself" 🙈
• target — TODO: NOT YET DOCUMENTED. same vibe, same mystery 💀
• pname — TODO: NOT YET DOCUMENTED. three for three, the documentation is NOT giving today 😭

---

✨ REPLY FIELDS ✨

• response_type — the type of this reply, and in this case it's XCB_GLX_GET_TEX_ENVFV. this field also shows up in the xcb_generic_reply_t, so you can use it to tell replies apart from each other 👑
• sequence — the sequence number of the last request the X11 server actually processed. like a little receipt number 🧾
• length — how long the reply is, measured in words — and a word is 4 bytes, no cap 📏
• n — TODO: NOT YET DOCUMENTED. mysterious. enigmatic. main character energy ✨
• datum — TODO: NOT YET DOCUMENTED. also mysterious, also not elaborating 🫶

---

✨ DESCRIPTION ✨

literally nothing here. the original DESCRIPTION section is empty. a blank canvas. a vibe. we love a minimalist queen 💅

---

✨ RETURN VALUE ✨

So it hands you back an xcb_glx_get_tex_envfv_cookie_t — a lil promise, basically. Errors? those don't get handled here, they get handled when you call the reply function xcb_glx_get_tex_envfv_reply. 🍓

But if you'd rather deal with errors in the event loop instead of right there, use xcb_glx_get_tex_envfv_unchecked. and yeah, go read xcb-requests(3) for the full deets, iykyk 🌈

---

✨ ERRORS ✨

good news bestie: this request does never generate any errors. flawless. no drama. we stay unbothered 🌸

---

✨ SEE ALSO ✨

the original SEE ALSO section is empty. nobody got linked. we're on our own out here 😭

---

✨ AUTHOR ✨

Generated from glx.xml. if you spot something wrong or wanna make it better, contact xcb@lists.freedesktop.org for corrections and improvements 💌

---

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

quick recap of the boring-but-important bits: this page is X Version 11, from libxcb 1.17.0, and it's the xcb_glx_get_tex_envfv(3) page — a.k.a. an XCB Request. love her, read her, use her, periodt. 💖✨🦋