xcb_xvmc_destroy_subpicture(3)
π xcb_xvmc_destroy_subpicture(3) π
okay bestie, this one is from XCB Requests (yes that's the manual name, we're in the XCB girlies now β¨). It's a little void request that goes and destroys a subpicture for you. Short page, but we're gonna give it the love it deserves. π«Ά
β¨ NAME β¨
xcb_xvmc_destroy_subpicture β
so likeβ¦ the description field here is literally empty. Nobody wrote one. The NAME section is just vibes and a dangling dash. π Not me being handed a blank canvas. We move.
β¨ SYNOPSIS β¨
First things first, you gotta pull in the header:
#include <xcb/xvmc.h>
π Request function π
Here's the actual call, character for character, no cap:
xcb_void_cookie_t xcb_xvmc_destroy_subpicture(xcb_connection_t *conn,
xcb_xvmc_subpicture_t subpicture_id);
it's giving "one line, two args, zero drama." π
β¨ REQUEST ARGUMENTS β¨
connβ the XCB connection to X11. Your link to the mothership, your little pipeline to the X server. πsubpicture_idβ okay so the original literally says TODO: NOT YET DOCUMENTED. and honestly? same. π We do not know more than the manpage tells us, and the manpage tells us nothing. Take it at face value: it's thexcb_xvmc_subpicture_tyou're yeeting into the void.
β¨ DESCRIPTION β¨
bestie. there is nothing here. The DESCRIPTION section is empty. A whole heading, zero words. It's giving "showed up to class, said nothing, left." π I cannot invent lore for you β the page genuinely does not describe what this does beyond the function name itself. Iconic minimalism, honestly.
β¨ RETURN VALUE β¨
It hands you back an xcb_void_cookie_t β a lil receipt for a request that doesn't really return data. π§Ύ
Errors (if any) have to be handled in the event loop. That's the deal.
If you'd rather handle errors directly withxcb_request_checkinstead, usexcb_xvmc_destroy_subpicture_checkedβ that's the checked twin, and it's right there for you. Seexcb-requests(3)for details. π
β¨ ERRORS β¨
Good news, bestie: this request does never generate any errors. Not one. Zero. A clean queen. πΈ
β¨ SEE ALSO β¨
literally nothing listed. the section header is there, the references are not. we respect the silence. π¦
β¨ AUTHOR β¨
Generated from xvmc.xml. If you spot something wrong or wanna improve it, contact xcb@lists.freedesktop.org for corrections and improvements. They're the ones holding the pen here. π
and that's the whole page, bestie! the footer energy is: X Version 11, libxcb 1.17.0, and the page name xcb_xvmc_destroy_subpicture(3) β no date on this one, she's timeless. β slay, go destroy that subpicture, and remember: empty DESCRIPTION sections are still valid, periodt. π
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms