xcb_render_query_filters(3)

💅 xcb_render_query_filters — the manual page (yes, xcb_render_query_filters(3), that one)

okay so bestie, pull up a chair, we're doing XCB Render filters today and honestly? it's giving ✨low-level-but-make-it-cute✨. This is the request that asks the X server "hey queen, what filters do you even have for this drawable?" 🎀

---

🌸 SYNOPSIS 🌸

First things first, you gotta bring in the header:

#include <xcb/render.h>

✨ Request function

xcb_render_query_filters_cookie_t
       xcb_render_query_filters(xcb_connection_t *conn,
       xcb_drawable_t drawable);

🦋 Reply datastructure

typedef struct xcb_render_query_filters_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t num_aliases;
    uint32_t num_filters;
    uint8_t  pad1[16];
} xcb_render_query_filters_reply_t;

💖 Reply function

xcb_render_query_filters_reply_t
       *xcb_render_query_filters_reply(xcb_connection_t *conn,
       xcb_render_query_filters_cookie_t cookie,
       xcb_generic_error_t **e);

🫶 Reply accessors

uint16_t *xcb_render_query_filters_aliases(const
       xcb_render_query_filters_request_t *reply);

int xcb_render_query_filters_aliases_length(const
       xcb_render_query_filters_reply_t *reply);

xcb_generic_iterator_t xcb_render_query_filters_aliases_end(const
       xcb_render_query_filters_reply_t *reply);

int xcb_render_query_filters_filters_length(const
       xcb_render_query_filters_reply_t *reply);

xcb_str_iterator_t xcb_render_query_filters_filters_iterator(const
       xcb_render_query_filters_reply_t *reply);

ngl, that accessor list is a whole vibe check on its own. Aliases get a pointer, a length and an end iterator; filters get a length and an iterator. Write that down. 📝

---

🌈 REQUEST ARGUMENTS

• conn — the XCB connection to X11. Your lil phone line to the server, basically. ☎️
• drawable — TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "we'll get to it" and then never did. 💀 Not my fault, I'm just the messenger.

---

👑 REPLY FIELDS

• response_type — the type of this reply, in this case XCB_RENDER_QUERY_FILTERS. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. It's like the name tag at a party so you know who you're talking to. 🎀
• sequence — the sequence number of the last request processed by the X11 server. It's the server going "yes babes, I got up to here." 🔢
• length — the length of the reply, in words (a word is 4 bytes). Do not forget the word-is-4-bytes part, I beg you. 😭
• num_aliases — TODO: NOT YET DOCUMENTED. the void stares back. 🕳️
• num_filters — TODO: NOT YET DOCUMENTED. also void. Also staring. 🙈

---

⭐ DESCRIPTION ⭐

so… there's literally nothing here. The section exists, the section is empty, the section is iconic for it actually. No description, no prose, no nothing. Just vibes and silence. 🦋

---

💜 RETURN VALUE

Returns an xcb_render_query_filters_cookie_t. 🍪 Errors have to be handled when calling the reply function xcb_render_query_filters_reply.

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

bestie, key thing: the cookie is not the answer. The cookie is the promise of an answer. Go get the reply. 🫶

---

🔥 ERRORS

This request does never generate any errors. Zero. None. Not a single one. She's unbothered, she's moisturized, she's in her lane. 👑

---

🎀 SEE ALSO

…nothing here either. Empty. Nada. The SEE ALSO section is out here living its best minimalist life. ✨

---

🌸 AUTHOR

Generated from render.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. If something's wrong, tell the humans at that address, not me, I'm just a girl with a keyboard. 💖

---

okay that's the whole page, love u, go forth and query those filters responsibly. 🌈

mwah 💋 — this one came from X Version 11, libxcb 1.17.0, and the page footer said xcb_render_query_filters(3) with no date in sight (rude, honestly), so that's the sign-off. byeee 🫶