XCB_RANDR_QUERY_PROVIDER_PROPERTY_VALID_VALUES(3)

💅 xcb_randr_query_provider_property — XCB Requests

okay bestie, welcome to the XCB Requests corner of the manual, this one's xcb_randr_query_provider_property(3) and it's giving "ask the X server about a provider property" energy. no cap, let's get into it 🦋

---

✨ NAME ✨

xcb_randr_query_provider_property — (the original leaves this blank too, so like… it's literally just the function name sitting there looking cute 🎀)

---

✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/randr.h>

🌸 Request function

xcb_randr_query_provider_property_cookie_t
       xcb_randr_query_provider_property(xcb_connection_t *conn,
       xcb_randr_provider_t provider, xcb_atom_t property);

🌸 Reply datastructure

this is the struct, the whole struct, and nothing but the struct. copy it exactly, she's iconic:

typedef struct xcb_randr_query_provider_property_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pending;
    uint8_t  range;
    uint8_t  immutable;
    uint8_t  pad1[21];
} xcb_randr_query_provider_property_reply_t;

🌸 Reply function

xcb_randr_query_provider_property_reply_t
       *xcb_randr_query_provider_property_reply(xcb_connection_t *conn,
       xcb_randr_query_provider_property_cookie_t cookie,
       xcb_generic_error_t **e);

🌸 Reply accessors

int32_t *xcb_randr_query_provider_property_valid_values(const
       xcb_randr_query_provider_property_request_t *reply);

int xcb_randr_query_provider_property_valid_values_length(const
       xcb_randr_query_provider_property_reply_t *reply);

xcb_generic_iterator_t
       xcb_randr_query_provider_property_valid_values_end(const
       xcb_randr_query_provider_property_reply_t *reply);

---

🫶 REQUEST ARGUMENTS 🫶

• conn — the XCB connection to X11. your lil hotline to the server, fr fr 💖
• provider — TODO: NOT YET DOCUMENTED. (the docs said "figure it out bestie", so I'm telling you exactly what they said 👑)
• property — TODO: NOT YET DOCUMENTED. (same vibe, the manpage is gatekeeping 🙈)

---

⭐ REPLY FIELDS ⭐

• response_type — the type of this reply, in this case XCB_RANDR_QUERY_PROVIDER_PROPERTY. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. lowkey the social security number of your reply 🎀
• sequence — the sequence number of the last request processed by the X11 server.
• length — the length of the reply, in words (and a word is 4 bytes, periodt).
• pending — TODO: NOT YET DOCUMENTED. 😭
• range — TODO: NOT YET DOCUMENTED. 😭
• immutable — TODO: NOT YET DOCUMENTED. 😭

---

🌈 DESCRIPTION 🌈

(nothing here, bestie — the original left it empty, so we're all just standing here respectfully 🕯️✨)

---

💜 RETURN VALUE 💜

Returns an xcb_randr_query_provider_property_cookie_t. okay so here's the tea: errors have to be handled when you call the reply function xcb_randr_query_provider_property_reply.

If you'd rather handle errors in the event loop instead, use xcb_randr_query_provider_property_unchecked. See xcb-requests(3) for the details, iykyk 📖

---

🍓 ERRORS 🍓

This request does never generate any errors. not one. zero. flawless. no drama, no trauma 💅

---

🧚 SEE ALSO 🧚

(the original lists nothing here — so there's literally nothing to see, and nothing to also 🌸)

---

👑 AUTHOR 👑

Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. be nice to them, they're doing their best 🫶

---

and that's the whole page, bestie!! 💖 it's from X Version 11, it's libxcb 1.17.0, it's xcb_randr_que...vider_property(3), and honestly? she ate. now go query that provider property, main character 🌟🦋✨