xcb_xvmc_create_context(3)

💅 xcb_xvmc_create_context

okay so bestie, welcome to section 3 of the manual — this is the XCB Requests girlies, and today's main character is xcb_xvmc_create_context. she's the one who sets up an XvMC context for you, and honestly? she's giving quiet-luxury utility. no cap.

---

✨ NAME ✨

xcb_xvmc_create_context — creates an XvMC context over XCB. (the original page's name line is just vibes and blank space, so we're keeping it real: it's the create-context request, periodt.)

---

🎀 SYNOPSIS 🎀

first things first, you gotta pull in the header:

#include <xcb/xvmc.h>

🦋 Request function

xcb_xvmc_create_context_cookie_t
       xcb_xvmc_create_context(xcb_connection_t *conn,
       xcb_xvmc_context_t context_id, xcb_xv_port_t port_id,
       xcb_xvmc_surface_t surface_id, uint16_t width, uint16_t height,
       uint32_t flags);

🦋 Reply datastructure

typedef struct xcb_xvmc_create_context_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint16_t width_actual;
    uint16_t height_actual;
    uint32_t flags_return;
    uint8_t  pad1[20];
} xcb_xvmc_create_context_reply_t;

🦋 Reply function

xcb_xvmc_create_context_reply_t
       *xcb_xvmc_create_context_reply(xcb_connection_t *conn,
       xcb_xvmc_create_context_cookie_t cookie,
       xcb_generic_error_t **e);

🦋 Reply accessors

uint32_t *xcb_xvmc_create_context_priv_data(const
       xcb_xvmc_create_context_request_t *reply);

int xcb_xvmc_create_context_priv_data_length(const
       xcb_xvmc_create_context_reply_t *reply);

xcb_generic_iterator_t xcb_xvmc_create_context_priv_data_end(const
       xcb_xvmc_create_context_reply_t *reply);

---

🌸 REQUEST ARGUMENTS 🌸

• conn — your XCB connection to X11. the whole pipeline, the moment, the lifeline fr.
• context_id — TODO: NOT YET DOCUMENTED. not me leaving this blank — the docs really said "mystery" 💀
• port_id — TODO: NOT YET DOCUMENTED. also a mystery box.
• surface_id — TODO: NOT YET DOCUMENTED. the silence is loud.
• width — TODO: NOT YET DOCUMENTED. unknown, iconic, mysterious.
• height — TODO: NOT YET DOCUMENTED. same energy.
• flags — TODO: NOT YET DOCUMENTED. undocumented and unbothered.

bestie these are literally marked TODO: NOT YET DOCUMENTED. in the source. i'm not making stuff up, i'm just being honest about the void 🙈

---

💖 REPLY FIELDS 💖

• response_type — the type of this reply, and in this case it's XCB_XVMC_CREATE_CONTEXT. this field is also chillin' in the xcb_generic_reply_t, so you can use it to tell replies apart from each other. vibe check: passed.
• sequence — the sequence number of the last request processed by the X11 server. the receipts, basically.
• length — the length of the reply, in words (a word is 4 bytes, bestie, write that down).
• width_actual — TODO: NOT YET DOCUMENTED. once again, a mystery.
• height_actual — TODO: NOT YET DOCUMENTED. the plot thickens (it does not).
• flags_return — TODO: NOT YET DOCUMENTED. we simply do not know.

---

🧚 DESCRIPTION 🧚

okay so… there's literally nothing here. the DESCRIPTION section is empty. no thoughts, head empty, slay ✨

---

⭐ RETURN VALUE ⭐

• Returns an xcb_xvmc_create_context_cookie_t. that's your little ticket, your receipt for the future.
• Errors have to be handled when calling the reply function xcb_xvmc_create_context_reply.
• If you want to handle errors in the event loop instead, use xcb_xvmc_create_context_unchecked. see xcb-requests(3) for details — iykyk.

---

🔥 ERRORS 🔥

This request does never generate any errors. zero drama, zero chaos, we love a low-maintenance queen 👑

---

💀 SEE ALSO 💀

nothing listed. the cross-references said "i'm out". we move.

---

👑 AUTHOR 👑

Generated from xvmc.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. they're literally asking for your feedback bestie, go be a helpful icon 🫶

---

and that's the whole page, babe. this came to you from X Version 11, rocking libxcb 1.17.0, and yes, the name on the tin is xcb_xvmc_create_context(3). go make some contexts, you absolute legend 💖✨🎀