xcb_randr_cha...ider_property(3)

✨ xcb_randr_change_provider_property ✨

okay bestie, so this one lives in the XCB Requests corner of the manual, and it's the little function from libxcb that pokes at a RandR provider's property 💅. It's giving "internal X11 plumbing but make it cute." Come sit with me.

---

🎀 NAME 🎀

xcb_randr_change_provider_property — and yeah, the description slot is literally empty in the source. Not me making that up, it's just... blank. A mystery. A vibe. 🦋

---

🌸 SYNOPSIS 🌸

First you gotta pull in the header:

#include <xcb/randr.h>

Then here's the request function itself, exactly as it is:

xcb_void_cookie_t
       xcb_randr_change_provider_property(xcb_connection_t *conn,
       xcb_randr_provider_t provider, xcb_atom_t property,
       xcb_atom_t type, uint8_t format, uint8_t mode,
       uint32_t num_items, const void *data);

She returns an xcb_void_cookie_t, and she takes a whole lil friend group of arguments. We're gonna meet all of them 👇

---

💖 REQUEST ARGUMENTS 💖

• conn — the XCB connection to X11. Your link to the whole party. 🔗
• provider — TODO: NOT YET DOCUMENTED. bestie I'm not gonna lie to you, the docs just say that. Straight up. 😭
• property — TODO: NOT YET DOCUMENTED. same energy, no cap.
• type — TODO: NOT YET DOCUMENTED. the mystery continues 🕵️
• format — TODO: NOT YET DOCUMENTED. nope, still nothing.
• mode — TODO: NOT YET DOCUMENTED. iconic of them to leave us hanging fr fr.
• num_items — TODO: NOT YET DOCUMENTED. 💀
• data — TODO: NOT YET DOCUMENTED. and that's the whole list, all seven of them undoc'd, periodt.

lowkey obsessed with how the entire argument list is just TODO: NOT YET DOCUMENTED. seven times. the way that this is a real shipped manual page... anyway, I'm telling you the truth, which is that there's no more info here. 🙈

---

🌈 DESCRIPTION 🌈

There is no description text in this page. Like, at all. That section is just vibes and empty space. So we move on, bestie. 💜

---

⭐ RETURN VALUE ⭐

She hands you back an xcb_void_cookie_t. That's it, that's the return.

Now — errors, if there are any, have to be handled in the event loop. That's the whole deal. 👑

If you'd rather handle errors directly with xcb_request_check instead, then use xcb_randr_change_provider_property_checked. And if you want the details on how any of that works, go read xcb-requests(3). 🫶

---

🦋 ERRORS 🦋

Okay this is the good news section: this request does never generate any errors. No errors. Zero. None. Clean. ✨

---

🔥 SEE ALSO 🔥

Nothing listed here! The section exists but it's empty. So... see also: nobody. 💅

---

👑 AUTHOR 👑

Generated from randr.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they wanna hear from you. 💌

---

and that's the whole page, bestie!! this one came from X Version 11, libxcb 1.17.0, with the manual page title xcb_randr_cha...ider_property(3) 💖 slay, you read the entire thing, I'm so proud of you 🌸✨