xcb_glx_get_visual_configs(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– xcb_glx_get_visual_configs β€” bestie edition πŸ’–

okay so this one lives in XCB Requests (that's the manual it's chillin' in), and it's basically the GLX request that goes "hey, tell me about the visual configs for this screen". no cap.


✨ NAME ✨

xcb_glx_get_visual_configs β€” the request that pulls the GLX visual configs for a screen πŸ¦‹


🌸 SYNOPSIS 🌸

#include <xcb/glx.h>

πŸ’… Request function

xcb_glx_get_visual_configs_cookie_t
       xcb_glx_get_visual_configs(xcb_connection_t *conn,
       uint32_t screen);

πŸŽ€ Reply datastructure

typedef struct xcb_glx_get_visual_configs_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t num_visuals;
    uint32_t num_properties;
    uint8_t  pad1[16];
} xcb_glx_get_visual_configs_reply_t;

✨ Reply function

xcb_glx_get_visual_configs_reply_t
       *xcb_glx_get_visual_configs_reply(xcb_connection_t *conn,
       xcb_glx_get_visual_configs_cookie_t cookie,
       xcb_generic_error_t **e);

🌈 Reply accessors

uint32_t *xcb_glx_get_visual_configs_property_list(const
       xcb_glx_get_visual_configs_request_t *reply);

int xcb_glx_get_visual_configs_property_list_length(const
       xcb_glx_get_visual_configs_reply_t *reply);

xcb_generic_iterator_t
       xcb_glx_get_visual_configs_property_list_end(const
       xcb_glx_get_visual_configs_reply_t *reply);

🫢 REQUEST ARGUMENTS 🫢

  • conn β€” your XCB connection to X11, the whole link-up bestie πŸ’œ
  • screen β€” TODO: NOT YET DOCUMENTED. yeah. nobody wrote it up yet. it's giving mystery πŸ™ˆ

πŸ‘‘ REPLY FIELDS πŸ‘‘

  • response_type β€” the type of this reply, and for this one it's XCB_GLX_GET_VISUAL_CONFIGS. this same field also lives in the xcb_generic_reply_t, so you can use it to tell replies apart from each other. iconic behaviour honestly ✨
  • sequence β€” the sequence number of the last request the X11 server actually processed, so you know where you're at πŸ”₯
  • length β€” the length of the reply, in words. and yes, a word here is 4 bytes, that's the unit, periodt πŸ’…
  • num_visuals β€” TODO: NOT YET DOCUMENTED. it's a mystery, we move πŸ•΅οΈ
  • num_properties β€” TODO: NOT YET DOCUMENTED. also a mystery. twin mysteries fr fr 😭

πŸ“ DESCRIPTION πŸ“

bestie. this section is literally empty in the original. nothing here. a whole void. we're not gonna make stuff up because that would be lying and lying is not the vibe πŸ’€

⭐ RETURN VALUE ⭐

It hands you back an xcb_glx_get_visual_configs_cookie_t. Cookies are cute but errors? errors have to be handled when you call the reply function xcb_glx_get_visual_configs_reply. no skipping that step πŸŽ€

If you'd rather handle errors in the event loop instead, use xcb_glx_get_visual_configs_unchecked. See xcb-requests(3) for the details, iykyk 🧚


🌸 ERRORS 🌸

This request does never generate any errors. like, none. zero. not a single one. slay πŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹

this section is empty in the original too 😭 nothing listed. we just vibe here.

πŸ’œ AUTHOR πŸ’œ

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. they're the ones keeping this whole thing alive, respect 🫢


and that's the whole page, bestie!! this came to you from X Version 11, libxcb 1.17.0, dated xcb_glx_get_visual_configs(3) β€” mwah, go forth and query those visual configs πŸ’…βœ¨πŸŽ€