XCB_RANDR_QUERY_OUTPUT_PROPERTY_VALID_VALUES_LENGTH(3)

💖 xcb_randr_query_output_property(3) 💖

okay bestie, so this is a page from the XCB Requests manual family, and it's literally about asking your X server "hey, what's up with this output property?" 🦋 it lives in the xcb/randr.h header, and ngl the docs are... a little shy on details. we're gonna work with what we've got, no cap.

---

✨ NAME ✨

xcb_randr_query_output_property — and that's it. the description line is empty, bestie. iconic of it honestly. 🙈

---

✨ SYNOPSIS ✨

first up, include the header:

#include <xcb/randr.h>

🎀 Request function

xcb_randr_query_output_property_cookie_t
       xcb_randr_query_output_property(xcb_connection_t *conn,
       xcb_randr_output_t output, xcb_atom_t property);

🎀 Reply datastructure

typedef struct xcb_randr_query_output_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_output_property_reply_t;

🎀 Reply function

xcb_randr_query_output_property_reply_t
       *xcb_randr_query_output_property_reply(xcb_connection_t *conn,
       xcb_randr_query_output_property_cookie_t cookie,
       xcb_generic_error_t **e);

🎀 Reply accessors

int32_t *xcb_randr_query_output_property_valid_values(const
       xcb_randr_query_output_property_request_t *reply);

int xcb_randr_query_output_property_valid_values_length(const
       xcb_randr_query_output_property_reply_t *reply);

xcb_generic_iterator_t
       xcb_randr_query_output_property_valid_values_end(const
       xcb_randr_query_output_property_reply_t *reply);

heads up: yes, that first accessor really does take an xcb_randr_query_output_property_request_t * while the other two take xcb_randr_query_output_property_reply_t *. we are reporting what the page says, bestie. 💅

---

🌸 REQUEST ARGUMENTS 🌸

• conn — the XCB connection to X11. your lil hotline to the server. 💜
• output — TODO: NOT YET DOCUMENTED. the docs simply did not show up for this one. 😭
• property — TODO: NOT YET DOCUMENTED. same energy, no notes. 😭

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, and in this case it's XCB_RANDR_QUERY_OUTPUT_PROPERTY. this field is also chillin' inside 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 this" energy. 👑
• sequence — the sequence number of the last request processed by the X11 server. it's the receipts. 🧾
• length — the length of the reply, in words (a word is 4 bytes). so multiply by 4 if you want bytes, iykyk. ⭐
• pending — TODO: NOT YET DOCUMENTED. 🙈
• range — TODO: NOT YET DOCUMENTED. 🙈
• immutable — TODO: NOT YET DOCUMENTED. 🙈

---

🦋 DESCRIPTION 🦋

...and that's the whole section, bestie. it's empty. the vibes are immaculate but the words are not there. 🫶

---

💅 RETURN VALUE 💅

it hands you back an xcb_randr_query_output_property_cookie_t. and listen — errors have to be handled when you call the reply function xcb_randr_query_output_property_reply. that's the moment of truth.

if you'd rather handle errors in the event loop instead, use xcb_randr_query_output_property_unchecked. peep xcb-requests(3) for the deets on how that works. ✨

---

🍓 ERRORS 🍓

this request does never generate any errors. clean. flawless. no drama. periodt. 💖

---

🧚 SEE ALSO 🧚

(empty, bestie. not a single reference. the page said nothing and left. 😭)

---

👑 AUTHOR 👑

generated from randr.xml. if you wanna send corrections or improvements, hit up xcb@lists.freedesktop.org. they're the main characters of this origin story. 🌟

---

okay that's the whole page bestie, mwah 💖 this one came from X Version 11, libxcb 1.17.0, and it's the xcb_randr_query_output_property(3) page — go query something iconic, you got this 🎀✨🦋