xcb_glx_are_textures_resident(3)

💖 xcb_glx_are_textures_resident(3) 💖

okay bestie, gather round, because we're doing an XCB Requests page today — it's xcb_glx_are_textures_resident(3), and yes it's a whole mouthful, say it three times fast, I dare you 🫶

This is the GLX "are these textures even resident tho" request. The NAME line? It's literally just the function name, a dash, and absolutely nothing after it 💀 iconic behaviour honestly. So like… the name is the name, no cap.

---

✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/glx.h>

🌸 Request function

xcb_glx_are_textures_resident_cookie_t
       xcb_glx_are_textures_resident(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, int32_t n, const
       uint32_t *textures);

🌸 Reply datastructure

typedef struct xcb_glx_are_textures_resident_reply_t {
    uint8_t          response_type;
    uint8_t          pad0;
    uint16_t         sequence;
    uint32_t         length;
    xcb_glx_bool32_t ret_val;
    uint8_t          pad1[20];
} xcb_glx_are_textures_resident_reply_t;

🌸 Reply function

xcb_glx_are_textures_resident_reply_t
       *xcb_glx_are_textures_resident_reply(xcb_connection_t *conn,
       xcb_glx_are_textures_resident_cookie_t cookie,
       xcb_generic_error_t **e);

🌸 Reply accessors

uint8_t *xcb_glx_are_textures_resident_data(const
       xcb_glx_are_textures_resident_request_t *reply);

int xcb_glx_are_textures_resident_data_length(const
       xcb_glx_are_textures_resident_reply_t *reply);

xcb_generic_iterator_t xcb_glx_are_textures_resident_data_end(const
       xcb_glx_are_textures_resident_reply_t *reply);

---

🎀 REQUEST ARGUMENTS 🎀

• conn — bestie this is just your XCB connection to X11. the whole phone line to the server, the main character of the connection world 👑
• context_tag — TODO: NOT YET DOCUMENTED. yeah girl, they left us on read on this one 🙈
• n — TODO: NOT YET DOCUMENTED. also left on read 💀
• textures — TODO: NOT YET DOCUMENTED. and this one too, the docs said "no thoughts, head empty" ✨

---

🦋 REPLY FIELDS 🦋

• response_type — the type of this reply, and in this case it's XCB_GLX_ARE_TEXTURES_RESIDENT. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other, like name tags at a party 🎀
• sequence — the sequence number of the last request the X11 server processed. the receipts, basically 🧾
• length — how long the reply is, in words — and a word here is 4 bytes, don't forget that part ⭐
• ret_val — TODO: NOT YET DOCUMENTED. the mystery box of fields, we simply do not know 🫶

---

🌈 DESCRIPTION 🌈

literally nothing here. the DESCRIPTION section is just vibes and silence. it's giving "we ran out of things to say" 😭

---

💜 RETURN VALUE 💜

So it returns an xcb_glx_are_textures_resident_cookie_t — cute lil cookie, hold onto it 🍪

Errors? You don't get them here, bestie. You have to handle those when you call the reply function xcb_glx_are_textures_resident_reply.

But if you'd rather handle your errors in the event loop instead, use xcb_glx_are_textures_resident_unchecked — see xcb-requests(3) for the deets, iykyk ✨

---

💅 ERRORS 💅

This request does never generate any errors. Not one. Zero. Clean sheet. slay. 🔥

---

⭐ SEE ALSO ⭐

…yeah there's nothing listed here. empty section, empty heart, we move on 💖

---

🌸 AUTHOR 🌸

Generated from glx.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they're the ones to tell 🫶

---

and that's the whole page, bestie!! this was X Version 11, libxcb 1.17.0, and you can find it filed under xcb_glx_are_textures_resident(3). periodt 💅✨🦋