XCB_RANDR_CONFIGURE_PROVIDER_PROPERTY(3)

✨ NAME ✨

xcb_randr_configure_provider_property — bestie, the name is the whole vibe here, because this page literally ships with no description. That's it. That's the entry. 💅

---

🦋 SYNOPSIS 🦋

Grab the header first, it's giving very "one include and you're in":

#include <xcb/randr.h>

🎀 Request function 🎀

Here's the signature, character for character, because we do not mess with the function signature, ever:

xcb_void_cookie_t
       xcb_randr_configure_provider_property(xcb_connection_t *conn,
       xcb_randr_provider_t provider, xcb_atom_t property,
       uint8_t pending, uint8_t range, uint32_t values_len, const
       int32_t *values);

It returns an xcb_void_cookie_t, it's a request, and yes bestie it has a lot of parameters. We move. 🌸

---

💖 REQUEST ARGUMENTS 💖

Okay so every single one of these is marked TODO: NOT YET DOCUMENTED. in the source. Not me being lazy — that's genuinely what the manpage says. The lore is incomplete. 😭 But here's the full cast list so you know who's who:

• conn — the XCB connection to X11. Your little telephone line to the server, the main character of every XCB call. ☎️
• provider — type xcb_randr_provider_t. TODO: NOT YET DOCUMENTED. 🙈
• property — type xcb_atom_t. TODO: NOT YET DOCUMENTED. 🙈
• pending — type uint8_t. TODO: NOT YET DOCUMENTED. 🙈
• range — type uint8_t. TODO: NOT YET DOCUMENTED. 🙈
• values_len — type uint32_t. TODO: NOT YET DOCUMENTED. 🙈
• values — type const int32_t *. TODO: NOT YET DOCUMENTED. 🙈

Ngl bestie, when the docs say TODO: NOT YET DOCUMENTED. they mean it. Don't go inventing meanings for pending and range in your head — that's how you end up in the group chat asking why nothing works. 💀

---

🌈 DESCRIPTION 🌈

There is no description. The DESCRIPTION section is empty. The void. The silence. The audacity. ✨

---

🔥 RETURN VALUE 🔥

It hands you back an xcb_void_cookie_t. And because it's a void request, any errors (if any) have to be handled over in your event loop — that's just how void cookies roll. 🍪

But wait, there's an option for the girlies who like to know immediately:

If you want to handle errors directly with xcb_request_check instead, use xcb_randr_configure_provider_property_checked. That's the checked variant, your impatient bestie. See xcb-requests(3) for details.

---

👑 ERRORS 👑

This request does never generate any errors. Zero. None. Clean. Slay. 💅

---

🧚 SEE ALSO 🧚

Nothing listed. Empty. The SEE ALSO section is out here living its minimalist era. 🦋

---

🍓 AUTHOR 🍓

Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements — so if you spot something, email the besties, they're literally asking for it. 🫶

---

And that's the page, babes — brought to you by X Version 11, libxcb 1.17.0, the one and only. Mwah. 💖