xcb_glx_query_context(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_query_context πŸ’–

okay bestie, welcome to the xcb_glx_query_context page from the XCB Requests fam β€” this is the part of the libxcb manual where we ask the X server "hey girl, what's up with this GLX context?" ✨


🌸 NAME 🌸

xcb_glx_query_context β€”

yes the NAME section is literally just vibes and a dash, the original said nothing more and I'm not about to make stuff up πŸ’…

✨ SYNOPSIS ✨

First things first, you gotta bring in the header:

#include <xcb/glx.h>

πŸŽ€ Request function

xcb_glx_query_context_cookie_t
       xcb_glx_query_context(xcb_connection_t *conn,
       xcb_glx_context_t context);

πŸŽ€ Reply datastructure

typedef struct xcb_glx_query_context_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t num_attribs;
    uint8_t  pad1[20];
} xcb_glx_query_context_reply_t;

πŸŽ€ Reply function

xcb_glx_query_context_reply_t
       *xcb_glx_query_context_reply(xcb_connection_t *conn,
       xcb_glx_query_context_cookie_t cookie, xcb_generic_error_t **e);

πŸŽ€ Reply accessors

uint32_t *xcb_glx_query_context_attribs(const
       xcb_glx_query_context_request_t *reply);
int xcb_glx_query_context_attribs_length(const
       xcb_glx_query_context_reply_t *reply);
xcb_generic_iterator_t xcb_glx_query_context_attribs_end(const
       xcb_glx_query_context_reply_t *reply);

πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11, aka your lil hotline to the server πŸ“ž
  • context β€” TODO: NOT YET DOCUMENTED. yeah babe, the docs simply did not show up to class that day 😭

🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_QUERY_CONTEXT. This field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other, like name tags at a party πŸŽ‰
  • sequence β€” the sequence number of the last request processed by the X11 server. it's giving receipt energy 🧾
  • length β€” the length of the reply, in words. and bestie, a word is 4 bytes, don't forget it πŸ’…
  • num_attribs β€” TODO: NOT YET DOCUMENTED. another mystery box, we love that for us πŸ™ˆ

πŸ’œ DESCRIPTION πŸ’œ

okay so this section is literally empty in the original. nothing. a void. a blank space. the manpage said ✨nothing✨ and I'm respecting the canon 🫢

⭐ RETURN VALUE ⭐

It hands you back an xcb_glx_query_context_cookie_t. πŸͺ

Errors? You don't deal with those here, babe β€” you handle them when you call the reply function xcb_glx_query_context_reply.

And if you'd rather handle errors in the event loop instead, use xcb_glx_query_context_unchecked. See xcb-requests(3) for the deets. iykyk ✨


πŸ”₯ ERRORS πŸ”₯

This request does never generate any errors. not a single one. she's unproblematic. she's the moment. periodt πŸ‘‘


🌟 SEE ALSO 🌟

the SEE ALSO section is empty in the original, no references were given, no crumbs left behind 😭

πŸŽ€ AUTHOR πŸŽ€

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. πŸ’Œ


okay that's the whole page bestie!! this one's from X Version 11, shipping with libxcb 1.17.0 β€” go forth and query those contexts, you absolute icon πŸ’…βœ¨πŸ¦‹πŸŒΈπŸ’–