xcb_glx_get_mapiv(3)
β¨ xcb_glx_get_mapiv β¨
okay bestie so this is a page from the XCB Requests chapter of the manual, it's xcb_glx_get_mapiv(3), and it lives in the xcb/glx.h header. it's a GLX request, it's giving "ask the X server for some GL map data" energy, and ngl the docs are lowkey a work in progress. let's get into it π
πΈ SYNOPSIS πΈ
first up, the include, always the include:
#include <xcb/glx.h>
π Request function π
xcb_glx_get_mapiv_cookie_t xcb_glx_get_mapiv(xcb_connection_t *conn,
xcb_glx_context_tag_t context_tag, uint32_t target,
uint32_t query);
π¦ Reply datastructure π¦
here's the whole lil struct, every field exactly where it belongs, no cap:
typedef struct xcb_glx_get_mapiv_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint8_t pad1[4];
uint32_t n;
int32_t datum;
uint8_t pad2[12];
} xcb_glx_get_mapiv_reply_t;
π Reply function π
xcb_glx_get_mapiv_reply_t
*xcb_glx_get_mapiv_reply(xcb_connection_t *conn,
xcb_glx_get_mapiv_cookie_t cookie, xcb_generic_error_t **e);
π«Ά Reply accessors π«Ά
the little helpers that reach into the reply for you:
int32_t *xcb_glx_get_mapiv_data(const xcb_glx_get_mapiv_request_t
*reply);
int xcb_glx_get_mapiv_data_length(const xcb_glx_get_mapiv_reply_t
*reply);
xcb_generic_iterator_t xcb_glx_get_mapiv_data_end(const
xcb_glx_get_mapiv_reply_t *reply);
π REQUEST ARGUMENTS π
connβ your XCB connection to X11. the whole vibe, the lifeline, the main character connection.context_tagβ TODO: NOT YET DOCUMENTED. bestie the docs simply did not elaborate πtargetβ TODO: NOT YET DOCUMENTED. againβ¦ nothing. iconic of them tbh.queryβ TODO: NOT YET DOCUMENTED. yeah same story π
π REPLY FIELDS π
response_typeβ the type of this reply, which in this case isXCB_GLX_GET_MAPIV. this field is ALSO chilling insidexcb_generic_reply_t, so you can use it to tell your replies apart from each other. very useful, very girlboss.sequenceβ the sequence number of the last request the X11 server processed.lengthβ how long the reply is, in words. and yes a word is 4 bytes, write that down πnβ TODO: NOT YET DOCUMENTED.datumβ TODO: NOT YET DOCUMENTED.
πΈ DESCRIPTION πΈ
literally nothing here. the section exists, the section is empty. we love a mysterious queen π
β¨ RETURN VALUE β¨
it hands you back an xcb_glx_get_mapiv_cookie_t. cookies are cute but errors? you gotta handle those yourself when you call the reply function xcb_glx_get_mapiv_reply.
and if you'd rather catch errors in the event loop instead? use xcb_glx_get_mapiv_unchecked. go read xcb-requests(3) for the full tea, fr fr.
π ERRORS π
this request does never generate any errors. zero. none. not a single one. slay π
π¦ SEE ALSO π¦
(the original page lists no references here β just an empty little section, and honestly? relatable.)
π AUTHOR π
Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β they said it, not me, so if you spot something off that's the address to hit up π
and that's the whole page bestie!! stay hydrated, handle your cookies, and remember: the source is X Version 11, the version is libxcb 1.17.0, and this little icon lives at xcb_glx_get_mapiv(3). mwah πβ¨π
π¦ 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