xcb_xvmc_destroy_surface(3)

📦
version 1.17.0 · 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ xcb_xvmc_destroy_surface ✨

okay bestie, this one lives in the XCB Requests corner of the manual (section 3, iykyk) and it's literally called xcb_xvmc_destroy_surface. 💅

🌸 NAME 🌸

xcb_xvmc_destroy_surface — that's it, that's the name (the manpage leaves the one-liner blank, no cap, so we're not gonna invent one 🙈)

🦋 SYNOPSIS 🦋

#include <xcb/xvmc.h>

✨ Request function ✨

xcb_void_cookie_t xcb_xvmc_destroy_surface(xcb_connection_t *conn,
       xcb_xvmc_surface_t surface_id);

🎀 REQUEST ARGUMENTS 🎀

  • conn — the XCB connection to X11. that's your lil hotline to the X server, periodt. 💖
  • surface_id — bestie... it literally says TODO: NOT YET DOCUMENTED. so that's all we got. not me being honest about it 🫶

💜 DESCRIPTION 💜

genuinely nothing here. the original page has an empty DESCRIPTION section, so there's no lore to spill. no invented facts in this group chat, ngl. 😭

🌈 RETURN VALUE 🌈

it hands you back an xcb_void_cookie_t. and the way that errors (if any) have to be handled in the event loop — yeah, that's the vibe. 🔥

if you'd rather handle errors directly with xcb_request_check instead, then use xcb_xvmc_destroy_surface_checked. see xcb-requests(3) for the details, bestie. 💖

👑 ERRORS 👑

this request does never generate any errors. zero. none. iconic behaviour honestly. ✨

🧚 SEE ALSO 🧚

...nothing listed. the section is empty. it's giving minimalist. 🎀

🍓 AUTHOR 🍓

Generated from xvmc.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 🫶

X Version 11 · libxcb 1.17.0 · mwah, that's the whole page, thanks for coming to my ted talk 💅🦋⭐

📦 where this page comes from