xcb_dri2_copy_region(3)

✨ xcb_dri2_copy_region — the dri2 copy_region request, explained by your favorite Unix girlie ✨

okay so bestie, we're in libxcb land, specifically the dri2 extension, and this page is the manual for xcb_dri2_copy_region 💖 it's a request function, it hands you back a cookie, and you come back later to get the reply. classic XCB pipeline energy. let's go 🌸

---

🌈 SYNOPSIS 🌈

#include <xcb/dri2.h>

🎀 Request function 🎀

xcb_dri2_copy_region_cookie_t
xcb_dri2_copy_region(xcb_connection_t *conn,
        xcb_drawable_t drawable, uint32_t region, uint32_t dest,
        uint32_t src);

🦋 Reply datastructure 🦋

typedef struct xcb_dri2_copy_region_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
} xcb_dri2_copy_region_reply_t;

💜 Reply function 💜

xcb_dri2_copy_region_reply_t
*xcb_dri2_copy_region_reply(xcb_connection_t *conn,
        xcb_dri2_copy_region_cookie_t cookie, xcb_generic_error_t **e);

---

💅 REQUEST ARGUMENTS 💅

• conn — your XCB connection to X11, the whole reason you're here, the main character tbh 🔥
• drawable — TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "we'll get to it" and then did not get to it 🙈
• region — TODO: NOT YET DOCUMENTED. same vibe, no cap
• dest — TODO: NOT YET DOCUMENTED. ngl, also undocumented
• src — TODO: NOT YET DOCUMENTED. and that's the whole argument squad, all four of the mystery ones 💀

---

🌟 REPLY FIELDS 🌟

• response_type — the type of this reply, and in this case it's XCB_DRI2_COPY_REGION ✨ this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other when they're all showing up in the same inbox 🫶
• sequence — the sequence number of the last request that the X11 server actually processed 📬
• length — the length of the reply, counted in words — and a word here is 4 bytes, periodt 🎀

---

🌸 DESCRIPTION 🌸

...so bestie, this section is literally empty. the manpage authors said "describe it" and the description said "no 💀". nothing to read here, moving on 🧚

---

👑 RETURN VALUE 👑

it returns an xcb_dri2_copy_region_cookie_t 🍪 and here's the thing — errors have to be handled when you call the reply function xcb_dri2_copy_region_reply. that's the deal, that's the contract.

but wait, if you'd rather handle errors in the event loop instead? use xcb_dri2_copy_region_unchecked 💜 and if you want the full tea on how that works, go read xcb-requests(3).

---

🚨 ERRORS 🚨

this request does never generate any errors. not a single one. zero. slay 💅

---

⭐ SEE ALSO ⭐

nothing listed here! iconic of the manpage honestly, it just vibes 🌈

---

💖 AUTHOR 💖

generated from dri2.xml. and if you spot something wrong or want to send improvements, contact xcb@lists.freedesktop.org — they literally asked for it, so don't be shy 📧

---

and that's the whole page bestie! this one came from X Version 11, libxcb 1.17.0, and it's filed under xcb_dri2_copy_region(3) 🦋 mwah, go copy some regions responsibly 💖✨