xcb_glx_get_pixel_mapuiv(3)

💖 xcb_glx_get_pixel_mapuiv(3) 💖

okay so bestie, welcome to the XCB Requests corner of the manual. this one's called xcb_glx_get_pixel_mapuiv, and yes it's a whole mouthful, but we're gonna get through it together. no cap. 🫶

---

✨ NAME ✨

xcb_glx_get_pixel_mapuiv — and that's literally all the original gives us here, bestie. no description. iconic mystery behavior. 💅

---

🌸 SYNOPSIS 🌸

first things first, you gotta bring in the header:

#include <xcb/glx.h>

🎀 Request function

xcb_glx_get_pixel_mapuiv_cookie_t
       xcb_glx_get_pixel_mapuiv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t map);

so you call this, you get a cookie back. not a snack cookie. a request cookie. keep it safe, you'll need it later. 🍓

🦋 Reply datastructure

this is the little struct the server's gonna hand you back, field by field:

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

look at all those pad fields just vibing there, doing absolutely nothing. main character energy honestly. ✨

🌈 Reply function

xcb_glx_get_pixel_mapuiv_reply_t
       *xcb_glx_get_pixel_mapuiv_reply(xcb_connection_t *conn,
       xcb_glx_get_pixel_mapuiv_cookie_t cookie,
       xcb_generic_error_t **e);

hand it your cookie, get your reply. that e pointer is where the errors come out to say hi. 👀

💜 Reply accessors

three little helpers to go rummaging through the reply:

uint32_t *xcb_glx_get_pixel_mapuiv_data(const
       xcb_glx_get_pixel_mapuiv_request_t *reply);

int xcb_glx_get_pixel_mapuiv_data_length(const
       xcb_glx_get_pixel_mapuiv_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_pixel_mapuiv_data_end(const
       xcb_glx_get_pixel_mapuiv_reply_t *reply);

(and yes, the first one really does say request_t in there. we don't question it. we just copy it exactly. periodt. 💀)

---

🔥 REQUEST ARGUMENTS 🔥

• conn — the XCB connection to X11. your lil lifeline to the server, bestie. 🌸
• context_tag — TODO: NOT YET DOCUMENTED. not me being left on read by the documentation 😭
• map — TODO: NOT YET DOCUMENTED. also left on read. we're both clueless here fr fr. 🙈

---

💅 REPLY FIELDS 💅

• response_type — the type of this reply, in this case XCB_GLX_GET_PIXEL_MAPUIV. it's also chillin' in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. very "which one of y'all is which" energy. 👑
• sequence — the sequence number of the last request processed by the X11 server. like a receipt number but for server activity. 🧚
• length — the length of the reply, in words. and a word is 4 bytes, before you ask. 📏
• n — TODO: NOT YET DOCUMENTED. mystery field, mystery vibe. ⭐
• datum — TODO: NOT YET DOCUMENTED. also a mystery. the lore is simply not there. 🌈

---

🎀 DESCRIPTION 🎀

literally nothing here in the original, bestie. an empty section. a blank canvas. the silence is deafening. 🤫

---

✨ RETURN VALUE ✨

it returns an xcb_glx_get_pixel_mapuiv_cookie_t. 🍪

and here's the important bit: errors have to be handled when you call the reply function xcb_glx_get_pixel_mapuiv_reply.

but if you'd rather handle errors in the event loop instead, use xcb_glx_get_pixel_mapuiv_unchecked. see xcb-requests(3) for the deets. you got options, bestie. 💖

---

🦋 ERRORS 🦋

this request does never generate any errors. zero. none. it's unbothered, it's moisturized, it's in its lane. ✨

---

🌸 SEE ALSO 🌸

bestie. it's empty. there is nothing to see here. we move. 💅

---

💜 AUTHOR 💜

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

---

and that's the whole thing! 🫶 this was rendered for you courtesy of X Version 11, libxcb 1.17.0, with the manual page title xcb_glx_get_pixel_mapuiv(3). slay, go forth, and remember to handle your errors at reply time. mwah. 💖🎀🦋