xcb_randr_lis...ut_properties(3)

✨ NAME ✨

xcb_randr_list_output_properties — bestie, this is the RandR request that lists all the properties hanging off an output 🎀 (the manpage literally leaves the description blank, so no spoilers here, we're just vibing with the name)

---

🌸 SYNOPSIS 🌸

#include <xcb/randr.h>

💅 Request function

xcb_randr_list_output_properties_cookie_t
xcb_randr_list_output_properties(xcb_connection_t *conn,
              xcb_randr_output_t output);

🦋 Reply datastructure

typedef struct xcb_randr_list_output_properties_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint16_t num_atoms;
    uint8_t  pad1[22];
} xcb_randr_list_output_properties_reply_t;

✨ Reply function

xcb_randr_list_output_properties_reply_t
       *xcb_randr_list_output_properties_reply(xcb_connection_t *conn,
              xcb_randr_list_output_properties_cookie_t cookie,
              xcb_generic_error_t **e);

🎀 Reply accessors

xcb_atom_t *xcb_randr_list_output_properties_atoms(const
              xcb_randr_list_output_properties_request_t *reply);

int xcb_randr_list_output_properties_atoms_length(const
              xcb_randr_list_output_properties_reply_t *reply);

xcb_generic_iterator_t xcb_randr_list_output_properties_atoms_end(const
              xcb_randr_list_output_properties_reply_t *reply);

---

🔥 REQUEST ARGUMENTS 🔥

• conn — the XCB connection to X11, aka your little phone line to the server, she's always on the other end waiting for you 💖
• output — TODO: NOT YET DOCUMENTED. yeah bestie, even the manpage said "idk yet" 🙈

---

💜 REPLY FIELDS 💜

• response_type — the type of this reply, which in this case is XCB_RANDR_LIST_OUTPUT_PROPERTIES. It also lives inside the xcb_generic_reply_t, so you can use it to tell your replies apart from each other, like name tags at a party 🎉
• sequence — the sequence number of the last request the X11 server actually processed, the receipts, the timeline, the lore 📜
• length — how long the reply is, measured in words (and a word here is 4 bytes, okay, write that down 📝)
• num_atoms — TODO: NOT YET DOCUMENTED. once again, mysterious. she's giving enigma 💀

---

🌈 DESCRIPTION 🌈

Literally nothing here. The original page left this section empty. She said "no thoughts, head empty" 🫶 Not me adding content that isn't there — nope, we keep it exactly as blank as the source, periodt.

---

👑 RETURN VALUE 👑

You get back an xcb_randr_list_output_properties_cookie_t. A cookie 🍪! And like any good cookie, it's not ready to eat immediately — errors have to be handled when you call the reply function xcb_randr_list_output_properties_reply.

But wait, there's an alternate route, bestie: if you'd rather handle errors in the event loop instead, use xcb_randr_list_output_properties_unchecked. Peep xcb-requests(3) for the full details on how that works ✨

---

💀 ERRORS 💀

This request does never generate any errors. Not one. Zero. Nada. She is unbothered, moisturised, in her lane 🌸

---

💖 SEE ALSO 💖

Nothing listed here, bestie. The original left it empty. Slay, I guess 💅

---

🧚 AUTHOR 🧚

Generated from randr.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they're literally waiting for your email 🫶

---

And that's the whole page, bestie! 💖 This little masterpiece comes to you from X Version 11, libxcb 1.17.0 — the exact version and date the original footer was rocking. Go forth and list those output properties, main character 🌟