xcb_xv_list_image_formats(3)
π xcb_xv_list_image_formats β bestie, it's an XCB Requests page (section 3) π
okay so picture this: you're deep in the X11 lore, you're vibing with Xv (that's the X Video extension, iykyk), and you wanna know which image formats this port is even serving. That's literally this request. She's giving "tell me your formats, king." β¨
No cap, the NAME section is just... a dash. Empty. Iconic of her honestly. π
β¨ SYNOPSIS β¨
First things first, you gotta let her in:
#include <xcb/xv.h>
π¦ Request function
xcb_xv_list_image_formats_cookie_t
xcb_xv_list_image_formats(xcb_connection_t *conn,
xcb_xv_port_t port);
π¦ Reply datastructure
typedef struct xcb_xv_list_image_formats_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t num_formats;
uint8_t pad1[20];
} xcb_xv_list_image_formats_reply_t;
π¦ Reply function
xcb_xv_list_image_formats_reply_t
*xcb_xv_list_image_formats_reply(xcb_connection_t *conn,
xcb_xv_list_image_formats_cookie_t cookie,
xcb_generic_error_t **e);
π¦ Reply accessors
xcb_xv_image_format_info_t *xcb_xv_list_image_formats_format(const
xcb_xv_list_image_formats_request_t *reply);
int xcb_xv_list_image_formats_format_length(const
xcb_xv_list_image_formats_reply_t *reply);
xcb_xv_image_format_info_iterator_t
xcb_xv_list_image_formats_format_iterator(const
xcb_xv_list_image_formats_reply_t *reply);
πΈ REQUEST ARGUMENTS πΈ
connβ your XCB connection to X11. Your lil hotline to the server, bestie πportβ TODO: NOT YET DOCUMENTED. Yeah girl, she's a mystery. Nobody wrote her up yet π
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_XV_LIST_IMAGE_FORMATS. Plot twist: this field also lives in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other. Very "which one of y'all is this" energy.sequenceβ the sequence number of the last request the X11 server got around to processing. She's the timeline, fr fr βlengthβ how long the reply is, in words (and a word here is4bytes, don't forget π«Ά)num_formatsβ TODO: NOT YET DOCUMENTED. Also a mystery. We stay humble π
π§ DESCRIPTION π§
...and that's it. That's the whole section. The DESCRIPTION is empty. She said "no thoughts, head empty" and honestly? Respect. π
π RETURN VALUE π
She hands you back an xcb_xv_list_image_formats_cookie_t. π
Heads up bestie: errors have to be handled when you call the reply function xcb_xv_list_image_formats_reply.
But wait β if you'd rather handle errors in the event loop instead, use xcb_xv_list_image_formats_unchecked. See xcb-requests(3) for the deets. Choose your fighter π
π₯ ERRORS π₯
This request does never generate any errors. Not one. Zero. She's an angel, she would never. πβ¨
π¦ SEE ALSO π¦
Nothing here either. Empty. A whole vibe. π
π AUTHOR π
Generated from xv.xml. If you spot something that needs fixing or improving, hit up xcb@lists.freedesktop.org β they're taking corrections, no cap. π§
okay and that's the whole page, bestie!! mwah π This lil masterpiece came to you courtesy of X Version 11, libxcb 1.17.0, and the one and only xcb_xv_list_image_formats(3). Stay slay, go list some formats, and remember: the DESCRIPTION is empty and that's valid π
πβ¨
π¦ 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