xcb_dbe_get_visual_info(3)
π xcb_dbe_get_visual_info β the XCB Requests girlies' guide π
okay bestie, so this is xcb_dbe_get_visual_info, straight out of the XCB Requests corner of the manual. it asks the X server for the visuals that support double buffering. that's the whole vibe. let's get into it π¦
β¨ NAME β¨
xcb_dbe_get_visual_info β Requests visuals that support double buffering π
πΈ SYNOPSIS πΈ
#include <xcb/dbe.h>
π Request function
xcb_dbe_get_visual_info_cookie_t
xcb_dbe_get_visual_info(xcb_connection_t *conn,
uint32_t n_drawables, const xcb_drawable_t *drawables);
π Reply datastructure
typedef struct xcb_dbe_get_visual_info_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint32_t n_supported_visuals;
uint8_t pad1[20];
} xcb_dbe_get_visual_info_reply_t;
π Reply function
xcb_dbe_get_visual_info_reply_t
*xcb_dbe_get_visual_info_reply(xcb_connection_t *conn,
xcb_dbe_get_visual_info_cookie_t cookie,
xcb_generic_error_t **e);
π Reply accessors
int xcb_dbe_get_visual_info_supported_visuals_length(const
xcb_dbe_get_visual_info_reply_t *reply);
xcb_dbe_visual_infos_iterator_t
xcb_dbe_get_visual_info_supported_visuals_iterator(const
xcb_dbe_get_visual_info_reply_t *reply);
π«Ά REQUEST ARGUMENTS π«Ά
connβ your XCB connection to X11. the link between you and the server, the situationship that actually works πn_drawablesβ TODO: NOT YET DOCUMENTED. yeah bestie, they left this one blank, we don't make stuff up around here πdrawablesβ TODO: NOT YET DOCUMENTED. same energy. mysterious. iconic. but undocumented fr fr.
π REPLY FIELDS π
response_typeβ the type of this reply, and in this case it'sXCB_DBE_GET_VISUAL_INFO. this field also lives in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other. it's giving name tag at a party πsequenceβ the sequence number of the last request processed by the X11 server. lowkey the server's receipt π§Ύlengthβ the length of the reply, in words. and yes, a word is 4 bytes here, that's just how they count πn_supported_visualsβ TODO: NOT YET DOCUMENTED. not me staring at this field with zero info π
π DESCRIPTION π
(no extra description was given, bestie β the section is literally empty. slay, minimalism β¨)
β RETURN VALUE β
it hands you back an xcb_dbe_get_visual_info_cookie_t. that's your little promise ticket ποΈ
errors? those get handled when you call the reply function xcb_dbe_get_visual_info_reply.
if you'd rather catch your errors in the event loop instead, usexcb_dbe_get_visual_info_unchecked. seexcb-requests(3)for the details, iykyk.
π ERRORS π
This request does never generate any errors. clean. flawless. no drama. periodt β¨
π₯ SEE ALSO π₯
π AUTHOR π
Generated from dbe.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. be nice, they're doing their best π«Ά
X Version 11 β libxcb 1.17.0 β and that's the whole page, bestie π β¨ mwah, go request some visuals, you ate π
π¦ 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