xcb_xv_query_port_attributes(3)
β¨ NAME β¨
xcb_xv_query_port_attributes β and thenβ¦ nothing, bestie π the description slot on this page is literally blank. We move anyway. π
π SYNOPSIS π
#include <xcb/xv.h>
Request function
xcb_xv_query_port_attributes_cookie_t
xcb_xv_query_port_attributes(xcb_connection_t *conn,
xcb_xv_port_t port);
Reply datastructure
typedef struct xcb_xv_query_port_attributes_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t num_attributes;
uint32_t text_size;
uint8_t pad1[16];
} xcb_xv_query_port_attributes_reply_t;
Reply function
xcb_xv_query_port_attributes_reply_t
*xcb_xv_query_port_attributes_reply(xcb_connection_t *conn,
xcb_xv_query_port_attributes_cookie_t cookie,
xcb_generic_error_t **e);
Reply accessors
int xcb_xv_query_port_attributes_attributes_length(const
xcb_xv_query_port_attributes_reply_t *reply);
xcb_xv_attribute_info_iterator_t
xcb_xv_query_port_attributes_attributes_iterator(const
xcb_xv_query_port_attributes_reply_t *reply);
π REQUEST ARGUMENTS π
connβ your XCB connection to X11, the lil thread tying you to the server π§΅portβ TODO: NOT YET DOCUMENTED. yeah girl, they left us hanging π
π¦ REPLY FIELDS π¦
response_typeβ the type of this reply, and in this case it'sXCB_XV_QUERY_PORT_ATTRIBUTES. This field also lives insidexcb_generic_reply_t, so you can use it to tell your replies apart from each other πsequenceβ the sequence number of the last request the X11 server actually processed π’lengthβ how long the reply is, in words (and a word is 4 bytes, that's the unit, periodt) πnum_attributesβ TODO: NOT YET DOCUMENTED. πtext_sizeβ TODO: NOT YET DOCUMENTED. π
πΈ DESCRIPTION πΈ
Soβ¦ the DESCRIPTION section on this page is completely empty. Not a single word. The original just has the heading and then bounces. Genuinely iconic of it β¨
π«Ά RETURN VALUE π«Ά
You get back an xcb_xv_query_port_attributes_cookie_t. Errors do not show up here β you have to deal with them when you call the reply function xcb_xv_query_port_attributes_reply. πͺ
And if you'd rather catch your errors in the event loop instead? Then use xcb_xv_query_port_attributes_unchecked β the details live in xcb-requests(3), go read it bestie π
π₯ ERRORS π₯
This request does never generate any errors. Not one. Zero. A clean slate, a peaceful life, we love that for you π
π SEE ALSO π
This section is empty on the original page, so there's nothing to send you off to. No links, no friends, just vibes π¦
π AUTHOR π
Generated from xv.xml. Got corrections or improvements? Contact xcb@lists.freedesktop.org β they'd love to hear from you fr fr π
And that's the whole page, bestie!! π This one came from X Version 11, shipped with libxcb 1.17.0, and it's the manual for xcb_xv_query_port_attributes(3). Go query those port attributes, you absolute main character ππ
β¨
π¦ 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