xcb_xvmc_create_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_create_surface(3) 💖

okay so bestie, welcome to the XCB Requests corner of the universe — this one lives in the libxcb crew, and it's the page for xcb_xvmc_create_surface. pull up a chair, we're doing X11 extension lore today 🎀

✨ NAME ✨

xcb_xvmc_create_surface -

and that's... it. that's the whole description. the dash is just sitting there. no notes. no explanation. iconic honestly 💅

✨ SYNOPSIS ✨

#include <xcb/xvmc.h>

🌸 Request function 🌸

xcb_xvmc_create_surface_cookie_t
       xcb_xvmc_create_surface(xcb_connection_t *conn,
       xcb_xvmc_surface_t surface_id, xcb_xvmc_context_t context_id);

🌸 Reply datastructure 🌸

typedef struct xcb_xvmc_create_surface_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad1[24];
} xcb_xvmc_create_surface_reply_t;

🌸 Reply function 🌸

xcb_xvmc_create_surface_reply_t
       *xcb_xvmc_create_surface_reply(xcb_connection_t *conn,
       xcb_xvmc_create_surface_cookie_t cookie,
       xcb_generic_error_t **e);

🌸 Reply accessors 🌸

uint32_t *xcb_xvmc_create_surface_priv_data(const
       xcb_xvmc_create_surface_request_t *reply);

int xcb_xvmc_create_surface_priv_data_length(const
       xcb_xvmc_create_surface_reply_t *reply);

xcb_generic_iterator_t xcb_xvmc_create_surface_priv_data_end(const
       xcb_xvmc_create_surface_reply_t *reply);
lowkey note that the first accessor takes an xcb_xvmc_create_surface_request_t *reply while the other two take an xcb_xvmc_create_surface_reply_t *reply. yes bestie, that's genuinely what the page says. i'm not gaslighting you 💀

✨ REQUEST ARGUMENTS ✨

  • conn — the XCB connection to X11. your lil hotline to the server, periodt 🫶
  • surface_id — TODO: NOT YET DOCUMENTED. yeah. it's giving mystery. 🙈
  • context_id — TODO: NOT YET DOCUMENTED. also a mystery. the devs said "we'll finish it later" and then didn't 😭

✨ REPLY FIELDS ✨

  • response_type — what kind of reply this is, and in this specific case it's XCB_XVMC_CREATE_SURFACE. this field also shows up in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. vibe check: passed ⭐
  • sequence — the sequence number of the last request that the X11 server actually processed.
  • length — how long the reply is, in words. and a word here is 4 bytes, so don't come at me with your human-word assumptions 🧚

✨ DESCRIPTION ✨

...it's empty bestie. the section exists and there is nothing inside it. a moment of silence 🕯️

✨ RETURN VALUE ✨

it hands you back an xcb_xvmc_create_surface_cookie_t. 🍪

errors? you gotta deal with those when you call the reply function xcb_xvmc_create_surface_reply.

but if you'd rather catch errors in the event loop instead, use xcb_xvmc_create_surface_unchecked. see xcb-requests(3) for the full tea on that. 💜

✨ ERRORS ✨

good news era: this request does never generate any errors. not one. zero. no cap. 🎉

✨ SEE ALSO ✨

(nothing here either. we love a minimalist queen 👑)

✨ AUTHOR ✨

Generated from xvmc.xml. wanna send corrections or improvements? contact xcb@lists.freedesktop.org — they're the ones who actually know things 🌈

and that's the whole page, bestie!! this one shipped with X Version 11, libxcb 1.17.0, and it goes by xcb_xvmc_create_surface(3) — ty for coming to my ted talk, mwah 💖✨🦋

📦 where this page comes from