xcb_render_qu..._index_values(3)

✨ NAME ✨

xcb_render_query_pict_index_values — the manpage is out here, part of the XCB Requests crew (that's your section 3, iykyk). And bestie, the description line in the original is literally blank 💀 so I'm not about to make up lore for you. The function name is the whole personality. Periodt.

---

🦋 SYNOPSIS 🦋

Okay so first you gotta pull in the header, no cap:

#include <xcb/render.h>

💅 Request function

xcb_render_query_pict_index_values_cookie_t
       xcb_render_query_pict_index_values(xcb_connection_t *conn,
       xcb_render_pictformat_t format);

🎀 Reply datastructure

typedef struct xcb_render_query_pict_index_values_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t num_values;
    uint8_t  pad1[20];
} xcb_render_query_pict_index_values_reply_t;

🌸 Reply function

xcb_render_query_pict_index_values_reply_t
       *xcb_render_query_pict_index_values_reply(xcb_connection_t *conn,
       xcb_render_query_pict_index_values_cookie_t cookie,
       xcb_generic_error_t **e);

🧚 Reply accessors

xcb_render_indexvalue_t *xcb_render_query_pict_index_values_values(const
       xcb_render_query_pict_index_values_request_t *reply);

int xcb_render_query_pict_index_values_values_length(const
       xcb_render_query_pict_index_values_reply_t *reply);

xcb_render_indexvalue_iterator_t
       xcb_render_query_pict_index_values_values_iterator(const
       xcb_render_query_pict_index_values_reply_t *reply);

---

🔥 REQUEST ARGUMENTS 🔥

• conn — your XCB connection to X11. Your group chat with the server, basically 💜
• format — TODO: NOT YET DOCUMENTED. Yeah. The docs said "figure it out" and clocked out 🙈 not me reading that in the source either.

---

👑 REPLY FIELDS 👑

• response_type — the type of this reply, and in this case it's XCB_RENDER_QUERY_PICT_INDEX_VALUES. This field is also chilling in the xcb_generic_reply_t, and you can use it to tell your replies apart from each other. It's giving name tag at a party 🎀
• sequence — the sequence number of the last request the X11 server actually processed. Slay, order matters.
• length — the length of the reply, measured in words. And a word is 4 bytes, so don't come at it with a character count, bestie.
• num_values — TODO: NOT YET DOCUMENTED. Again!! 😭 the mystery continues.

---

🌈 DESCRIPTION 🌈

The original page leaves this section empty. No prose, no vibes, no nothing. We are not inventing behaviour, that's the rule 🫶

---

⭐ RETURN VALUE ⭐

Returns an xcb_render_query_pict_index_values_cookie_t. That's your little receipt, and the errors? You have to handle them when you call the reply function xcb_render_query_pict_index_values_reply. So don't just toss the cookie in a drawer and walk away, that's how you end up with silent problems 💀

But if you'd rather handle your errors inside the event loop instead, use xcb_render_query_pict_index_values_unchecked. See xcb-requests(3) for the details — it's the lore drop you need.

---

💖 ERRORS 💖

This request does never generate any errors. Iconic. Flawless. Zero drama. Not one single red flag 😌✨

---

🔍 SEE ALSO 🔍

This section is blank in the original — no references listed. Nothing to link, nothing to gatekeep 🙈

---

🌸 AUTHOR 🌸

Generated from render.xml. Got corrections or improvements? Hit up xcb@lists.freedesktop.org — they're the main characters of this story 👑

---

and that's the whole page, bestie 💅 X Version 11, libxcb 1.17.0 — that's the version and the source, right there at the bottom of the original, and now it's right here at the bottom of your heart. Stay hydrated, read your return values, and go handle those errors 🦋💜