xcb_render_query_pict_formats(3)

✨ xcb_render_query_pict_formats ✨

okay bestie, quick vibe check: this page lives in the XCB Requests manual section (that's the manual name, we're folding it in here instead of copy-pasting the header line, you're welcome 💅). It's xcb_render_query_pict_formats(3) and it's the function that asks the X server "hey, what picture formats do you even have??" 🎨✨

---

🌸 NAME 🌸

xcb_render_query_pict_formats —

not me showing up to the NAME section with literally nothing to say 💀 the original is just a bare dash. iconic behavior honestly. the name is the function name, that's the whole thing, periodt.

---

🦋 SYNOPSIS 🦋

#include <xcb/render.h>

💖 Request function 💖

xcb_render_query_pict_formats_cookie_t
       xcb_render_query_pict_formats(xcb_connection_t *conn,

💖 Reply datastructure 💖

typedef struct xcb_render_query_pict_formats_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t num_formats;
    uint32_t num_screens;
    uint32_t num_depths;
    uint32_t num_visuals;
    uint32_t num_subpixel;
    uint8_t  pad1[4];
} xcb_render_query_pict_formats_reply_t;

💖 Reply function 💖

xcb_render_query_pict_formats_reply_t
       *xcb_render_query_pict_formats_reply(xcb_connection_t *conn,
       xcb_render_query_pict_formats_cookie_t cookie,
       xcb_generic_error_t **e);

💖 Reply accessors 💖

xcb_render_pictforminfo_t *xcb_render_query_pict_formats_formats(const
       xcb_render_query_pict_formats_request_t *reply);

int xcb_render_query_pict_formats_formats_length(const
       xcb_render_query_pict_formats_reply_t *reply);

xcb_render_pictforminfo_iterator_t
       xcb_render_query_pict_formats_formats_iterator(const
       xcb_render_query_pict_formats_reply_t *reply);

int xcb_render_query_pict_formats_screens_length(const
       xcb_render_query_pict_formats_reply_t *reply);

xcb_render_pictscreen_iterator_t
       xcb_render_query_pict_formats_screens_iterator(const
       xcb_render_query_pict_formats_reply_t *reply);

uint32_t *xcb_render_query_pict_formats_subpixels(const
       xcb_render_query_pict_formats_request_t *reply);

int xcb_render_query_pict_formats_subpixels_length(const
       xcb_render_query_pict_formats_reply_t *reply);

xcb_generic_iterator_t xcb_render_query_pict_formats_subpixels_end(const
       xcb_render_query_pict_formats_reply_t *reply);

like, look at all those accessors 🫶 they're your little grabby hands for pulling pieces out of the reply. slay.

---

💅 REQUEST ARGUMENTS 💅

• conn — The XCB connection to X11. it's your lil phone line to the server, bestie ☎️ no connection, no formats, no nothing.

---

🎀 REPLY FIELDS 🎀

• response_type — The type of this reply, in this case XCB_RENDER_QUERY_PICT_FORMATS. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. (it's the lil name tag at the party so you know which reply just walked in 💌)
• sequence — The sequence number of the last request processed by the X11 server.
• length — The length of the reply, in words (a word is 4 bytes).
• num_formats — TODO: NOT YET DOCUMENTED. 😭 (the docs really said "figure it out" — we're not gonna invent lore, so we're keeping it exactly as-is, no cap)
• num_screens — TODO: NOT YET DOCUMENTED. 🙈
• num_depths — TODO: NOT YET DOCUMENTED. 💀
• num_visuals — TODO: NOT YET DOCUMENTED. ✨
• num_subpixel — TODO: NOT YET DOCUMENTED. 🍓

fr fr, those five are undocumented in the source. we are NOT guessing at behavior. the vibes are mysterious and that's just how it is.

---

🌈 DESCRIPTION 🌈

...there isn't one. the DESCRIPTION section in the original is literally empty. the way that the manpage just skipped straight to RETURN VALUE 💀 it's giving "no thoughts, head empty, still slays." nothing to report, bestie, and we're not making anything up.

---

👑 RETURN VALUE 👑

Returns an xcb_render_query_pict_formats_cookie_t. Errors have to be handled when calling the reply function xcb_render_query_pict_formats_reply.

If you want to handle errors in the event loop instead, use xcb_render_query_pict_formats_unchecked. See xcb-requests(3) for details.

okay so the cookie is like the receipt you get at the counter 🧾 — the request is already on its way, and the actual answer (or the error) shows up when you come back with that receipt. that's the whole deal with _unchecked too: you grab the cookie, you deal with the fallout later in your event loop.

---

💀 ERRORS 💀

This request does never generate any errors.

zero. none. not a single one. it's the good kid of X requests 😇✨

---

🔥 SEE ALSO 🔥

...nothing here either. the SEE ALSO section in the original is empty, so there are no references to pass along. no friends, no neighbors, just this one function doing its thing 💅

---

💜 AUTHOR 💜

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

---

okay that's the whole page bestie, you ate it up 🫶 this one came from X Version 11, libxcb 1.17.0 — go query some picture formats, you main character, and remember: no invented lore, only facts 💖✨🌈