xcb_xv_put_video(3)

💖 xcb_xv_put_video — the XCB request that yeets video into a drawable 💖

okay bestie, sit down, we're doing XCB today 🫶 this one lives in the XCB Requests corner of the manual, page xcb_xv_put_video(3), and it's a request function — meaning you're asking the X server to do a thing, not waiting around for a return value like some nerd. slay.

---

✨ SYNOPSIS ✨

first things first, you gotta pull in the header, no cap:

#include <xcb/xv.h>

🎀 Request function 🎀

here's the whole vibe, character for character, don't you dare typo it:

xcb_void_cookie_t xcb_xv_put_video(xcb_connection_t *conn,
       xcb_xv_port_t port, xcb_drawable_t drawable, xcb_gcontext_t gc,
       int16_t vid_x, int16_t vid_y, uint16_t vid_w, uint16_t vid_h,
       int16_t drw_x, int16_t drw_y, uint16_t drw_w, uint16_t drw_h);

---

🌸 REQUEST ARGUMENTS 🌸

the way there are so many of these 😭 every single one, coming right up:

• conn — bestie, this is your XCB connection to X11. your whole line to the server. iconic. 💅
• port — TODO: NOT YET DOCUMENTED. yeah. the docs simply did not show up. it's giving mystery. 🙈
• drawable — TODO: NOT YET DOCUMENTED. (same energy, we know nothing, ngl)
• gc — TODO: NOT YET DOCUMENTED. (a graphics context shaped hole in our hearts 💀)
• vid_x — TODO: NOT YET DOCUMENTED.
• vid_y — TODO: NOT YET DOCUMENTED.
• vid_w — TODO: NOT YET DOCUMENTED.
• vid_h — TODO: NOT YET DOCUMENTED.
• drw_x — TODO: NOT YET DOCUMENTED.
• drw_y — TODO: NOT YET DOCUMENTED.
• drw_w — TODO: NOT YET DOCUMENTED.
• drw_h — TODO: NOT YET DOCUMENTED.

like… every single one is a TODO?? the whole argument list is running on vibes alone and honestly? respect. 🧚

---

🦋 DESCRIPTION 🦋

so, um. there is literally nothing here. the DESCRIPTION section is empty. it's giving "I'll write it later" and later never came. 🌈

no extra lore, no secret tips, no invented behaviour from me — if the original says nothing, I say nothing. periodt.

---

👑 RETURN VALUE 👑

it hands you back an xcb_void_cookie_t. cute little cookie. 🍓 but here's the tea — because it's void, any errors (if any) have to be handled over in the event loop. the cookie doesn't spill.

but if you're the type who wants to handle errors directly, no event loop detour, then use xcb_xv_put_video_checked instead. same energy, just checked. and go read xcb-requests(3) for the full details, iykyk. 📖

---

💀 ERRORS 💀

good news bestie: this request does never generate any errors. zero. none. it's a clean queen. 🔥

---

🌟 SEE ALSO 🌟

nothing here either. empty. a lil void. the SEE ALSO section said "no thoughts, head empty" and honestly we love that for it. 🎀

---

💜 AUTHOR 💜

this page was generated from xv.xml. if you spot something wrong and wanna fix it or make it better, hit up xcb@lists.freedesktop.org — they take corrections and improvements, fr fr. 🫶

---

and that's the whole page, bestie! mwah 💅 this lil legend came to you from X Version 11 and libxcb 1.17.0, on the xcb_xv_put_video(3) page — go forth and put that video, no cap. ✨🌈💖