xcb_glx_get_booleanv(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_booleanv β€” XCB Requests era

okay bestie, gather round, because this one is a libxcb page (the XCB Requests girlies) and she's called xcb_glx_get_booleanv. That's the name, that's the vibe, and the original page's NAME line literally just says the name and then nothing else. Iconic minimalism, honestly. She said "my name is enough." πŸ’–


✨ SYNOPSIS ✨

First things first, you gotta bring in the header:

#include <xcb/glx.h>

πŸŽ€ Request function

xcb_glx_get_booleanv_cookie_t
       xcb_glx_get_booleanv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, int32_t pname);

πŸ¦‹ Reply datastructure

typedef struct xcb_glx_get_booleanv_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad1[4];
    uint32_t n;
    uint8_t  datum;
    uint8_t  pad2[15];
} xcb_glx_get_booleanv_reply_t;

🌸 Reply function

xcb_glx_get_booleanv_reply_t
       *xcb_glx_get_booleanv_reply(xcb_connection_t *conn,
       xcb_glx_get_booleanv_cookie_t cookie, xcb_generic_error_t **e);

🫢 Reply accessors

uint8_t *xcb_glx_get_booleanv_data(const xcb_glx_get_booleanv_request_t
       *reply);

int xcb_glx_get_booleanv_data_length(const xcb_glx_get_booleanv_reply_t
       *reply);

xcb_generic_iterator_t xcb_glx_get_booleanv_data_end(const
       xcb_glx_get_booleanv_reply_t *reply);

πŸ’œ REQUEST ARGUMENTS

  • conn β€” the XCB connection to X11, aka your little hotline to the server. she's the main character, she carries everything.
  • context_tag β€” TODO: NOT YET DOCUMENTED. yeah babe, the docs said "not yet" and honestly same. πŸ™ˆ
  • pname β€” TODO: NOT YET DOCUMENTED. also a mystery. the lore is not there yet, bestie, we do not make things up in this house.

πŸ”₯ REPLY FIELDS

  • response_type β€” the type of this reply, and in this specific case it's XCB_GLX_GET_BOOLEANV. This field is ALSO chillin' inside xcb_generic_reply_t, so you can peek at it to tell your replies apart from each other. very "who dis" energy. πŸ‘‘
  • sequence β€” the sequence number of the last request processed by the X11 server. her receipts, her timeline. ⭐
  • length β€” the length of the reply, measured in words. and yes, a word here is 4 bytes, do not forget it. πŸ’…
  • n β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • datum β€” TODO: NOT YET DOCUMENTED. πŸ“

🌈 DESCRIPTION

okay so the original DESCRIPTION section is just... empty. she's giving silence, she's giving mystery, she's giving "figure it out yourself." we respect her journey. πŸ’–


✨ RETURN VALUE

She hands you back an xcb_glx_get_booleanv_cookie_t. that's your little ticket, your little promise ring. πŸ’

But listen β€” errors have to be handled when you call the reply function xcb_glx_get_booleanv_reply. that's the moment of truth, no skipping it.

If you'd rather handle errors in the event loop instead, use xcb_glx_get_booleanv_unchecked. See xcb-requests(3) for the details, because she explains it better than I can fr fr.


🧚 ERRORS

Good news, bestie: this request does never generate any errors. not a single one. she is unproblematic. she is the moment. periodt. ✨


🌸 SEE ALSO

...nothing. the original SEE ALSO section is completely empty, no references, no friends, nothing. she's solo in the group chat. πŸ₯²


πŸ’œ AUTHOR

Generated from glx.xml. If you wanna send corrections and improvements, hit up xcb@lists.freedesktop.org. they're listening, they're just vibing in the mailing list. 🫢


and that's the whole page, angel πŸ’– this one came from X Version 11, libxcb 1.17.0, and she's filed under xcb_glx_get_booleanv(3). slay, read her, love her, close the man page. πŸ‘‘πŸ¦‹πŸŒΈ