xcb_xv_query_adaptors(3)
β¨ xcb_xv_query_adaptors β¨
okay bestie, welcome to xcb_xv_query_adaptors(3) π this is one of the XCB Requests girlies, and she's here to let you ask the X11 server "heyβ¦ what adaptors do we have?" no cap. it lives in the xv extension corner of libxcb, and honestly? she's giving very "quiet but essential" energy. πΈ
π SYNOPSIS
first up, include the thing or nothing works, periodt:
#include <xcb/xv.h>
π Request function
xcb_xv_query_adaptors_cookie_t
xcb_xv_query_adaptors(xcb_connection_t *conn,
xcb_window_t window);
π¦ Reply datastructure
this is the lil struct the server hands back, look at her:
typedef struct xcb_xv_query_adaptors_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint16_t num_adaptors;
uint8_t pad1[22];
} xcb_xv_query_adaptors_reply_t;
π Reply function
xcb_xv_query_adaptors_reply_t
*xcb_xv_query_adaptors_reply(xcb_connection_t *conn,
xcb_xv_query_adaptors_cookie_t cookie, xcb_generic_error_t **e);
π Reply accessors
these are the lil helpers that peek inside the reply for you, iykyk:
int xcb_xv_query_adaptors_info_length(const
xcb_xv_query_adaptors_reply_t *reply);
xcb_xv_adaptor_info_iterator_t xcb_xv_query_adaptors_info_iterator(const
xcb_xv_query_adaptors_reply_t *reply);
πΈ REQUEST ARGUMENTS
connβ your XCB connection to X11, aka the lil phone line to the server. literally the whole reason any of this works. π«ΆwindowβTODO: NOT YET DOCUMENTED.yeah bestie, the docs said "we'll get to it" and then never did π it's a window, that's the vibe, that's all we got.
π REPLY FIELDS
response_typeβ the type of this reply, which in this case isXCB_XV_QUERY_ADAPTORS. this field also chills in thexcb_generic_reply_t, so you can use it to tell replies apart from each other. it's the name tag at the party πsequenceβ the sequence number of the last request processed by the X11 server. so you always know where you are in the timeline β³lengthβ the length of the reply, in words. and because someone WILL ask: a word is 4 bytes. iconic unit choice, no notes β¨num_adaptorsβTODO: NOT YET DOCUMENTED.again!! the mystery continues π΅οΈβοΈ it's a count of adaptors, that's the tea we have.
π DESCRIPTION
nothing here bestie. the DESCRIPTION section is literally empty. an empty canvas. a blank page. we simply do not have description lore today π
π₯ RETURN VALUE
Returns an xcb_xv_query_adaptors_cookie_t. πͺ
errors have to be handled when you call the reply function xcb_xv_query_adaptors_reply.
but if you'd rather handle errors in the event loop instead, usexcb_xv_query_adaptors_unchecked. seexcb-requests(3)for the details, bestie, it's all there π
π§ ERRORS
This request does never generate any errors. not one. zero. she's unproblematic and we LOVE that for her πβ¨
π SEE ALSO
empty. nothing. the SEE ALSO section is a void and we respect her privacy π
π AUTHOR
Generated from xv.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. like, fr fr, if something's wrong, tell them, they're nice π«Ά
okay that's the whole page, you ate that, go forth and query those adaptors π β¨
big kisses from X Version 11, libxcb 1.17.0 π the manual page header said xcb_xv_query_adaptors(3) and yes she's still that girl π mwah, bye bestie!! πΈπ¦π
π¦ 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