xcb_xfixes_set_region(3)

💖 NAME 💖

xcb_xfixes_set_region — and bestie, that's it. That's the whole description. The dash is just sitting there with nothing after it, no cap. The actual docs did not come to serve looks today, but we're still gonna work with what we've got. This one lives in XCB Requests, the little family of manual pages for talking to your X server through XCB, and it's the 3 girlie (a library function page, iykyk).

---

✨ SYNOPSIS ✨

First things first, you gotta pull in the header, like so:

#include <xcb/xfixes.h>

🎀 Request function 🎀

And here's the function signature, verbatim, don't @ me:

xcb_void_cookie_t xcb_xfixes_set_region(xcb_connection_t *conn,
       xcb_xfixes_region_t region, uint32_t rectangles_len, const
       xcb_rectangle_t *rectangles);

---

🦋 REQUEST ARGUMENTS 🦋

• conn — the XCB connection to X11. She's your whole line to the server, your main character, your ride-or-die. No conn, no request, periodt.
• region — TODO: NOT YET DOCUMENTED. Yeah bestie, the docs said "we'll do it later" and then simply never did. 😭
• rectangles_len — TODO: NOT YET DOCUMENTED. Also left on read by whoever was supposed to write this.
• rectangles — TODO: NOT YET DOCUMENTED. Same energy. The vibe is mystery, the facts are absent. 💀

Not me having to type TODO: NOT YET DOCUMENTED three times in a row. I'm not making this up, it's genuinely what the page says, and I will NOT be inventing behaviour that isn't there. 🙈

---

🌸 DESCRIPTION 🌸

Nothing. Truly nothing. The section exists, it has a heading, and then it is empty. It's giving minimalist. It's giving "left as an exercise for the reader." It's giving silence in the group chat after someone asks what the function actually does. 🫶

---

🔥 RETURN VALUE 🔥

She returns an xcb_void_cookie_t. That's the whole return situation.

And listen, because this matters: errors (if any) have to be handled in the event loop. You don't get them handed to you right here, no ma'am, you gotta go catch them later.

But if you'd rather handle errors directly, with xcb_request_check instead? Then babe, use xcb_xfixes_set_region_checked. Different function, different energy. Head over to xcb-requests(3) for all the deets on how that works.

---

⭐ ERRORS ⭐

This request does never generate any errors.

Not "rarely". Not "sometimes". Never. Zero. Zilch. A spotless record, an angel, no drama on this timeline. 💅

---

🌈 SEE ALSO 🌈

Nothing here either, bestie. Empty. A little void where the cross-references should be. The one crumb we did get lives up in RETURN VALUE (xcb-requests(3)), so go peek at that if you need it. 🦋

---

👑 AUTHOR 👑

Generated from xfixes.xml. If something's wrong or you wanna make it better, contact xcb@lists.freedesktop.org for corrections and improvements. The people who actually maintain this are the real MVPs, fr fr. 🫶

---

And that's a wrap, bestie! ✨ This little page came to you from X Version 11, running libxcb 1.17.0, and it's the xcb_xfixes_set_region(3) manual page — short, sweet, and honestly 40% TODO by volume. Slay, go set some regions (responsibly). 💖🎀🌸