xcb_glx_get_pixel_mapusv(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_pixel_mapusv β€” bestie, it's a libxcb manual page

okay so this is xcb_glx_get_pixel_mapusv(3) from the XCB Requests girlies, and yes she is serving GLX pixel map energy. sit down, grab a strawberry, we're doing this together πŸ“βœ¨


✨ NAME ✨

xcb_glx_get_pixel_mapusv β€” the manpage literally gives us no description here, so we're just gonna hold hands and read the synopsis like the icons we are πŸ’–


🌸 SYNOPSIS 🌸

#include <xcb/glx.h>

πŸŽ€ Request function

xcb_glx_get_pixel_mapusv_cookie_t
       xcb_glx_get_pixel_mapusv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t map);

πŸ¦‹ Reply datastructure

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

🌈 Reply function

xcb_glx_get_pixel_mapusv_reply_t
       *xcb_glx_get_pixel_mapusv_reply(xcb_connection_t *conn,
       xcb_glx_get_pixel_mapusv_cookie_t cookie,
       xcb_generic_error_t **e);

πŸ’œ Reply accessors

uint16_t *xcb_glx_get_pixel_mapusv_data(const
       xcb_glx_get_pixel_mapusv_request_t *reply);

int xcb_glx_get_pixel_mapusv_data_length(const
       xcb_glx_get_pixel_mapusv_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_pixel_mapusv_data_end(const
       xcb_glx_get_pixel_mapusv_reply_t *reply);

🫢 REQUEST ARGUMENTS 🫢

  • conn β€” your connection to X11, the little string that keeps you and the server connected, no cap. πŸ’«
  • context_tag β€” TODO: NOT YET DOCUMENTED. yeah bestie the docs ghosted us on this one 😭
  • map β€” TODO: NOT YET DOCUMENTED. also a mystery, also iconic for it πŸ•΅οΈβ™€οΈ

πŸ‘‘ REPLY FIELDS πŸ‘‘

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_GET_PIXEL_MAPUSV. this field is also chillin' in the xcb_generic_reply_t, so you can use it to tell replies apart from each other. vibe check passed βœ…
  • sequence β€” the sequence number of the last request the X11 server processed. like a lil receipt number for your request 🧾
  • length β€” how long the reply is, in words (and heads up, a word is 4 bytes here, not vibes). πŸ“
  • n β€” TODO: NOT YET DOCUMENTED. πŸ’€
  • datum β€” TODO: NOT YET DOCUMENTED. πŸ’€

πŸ’– DESCRIPTION πŸ’–

so... the DESCRIPTION section is literally empty. nothing. a void. the manual page said "no thoughts, head empty" πŸ•³οΈβœ¨

we're respecting her silence, periodt.


⭐ RETURN VALUE ⭐

She returns an xcb_glx_get_pixel_mapusv_cookie_t, bestie. and listen β€” errors have to be handled when you call the reply function xcb_glx_get_pixel_mapusv_reply. that's the moment of truth, that's the main character scene.

If you'd rather handle errors in the event loop instead, use xcb_glx_get_pixel_mapusv_unchecked. See xcb-requests(3) for details β€” she explains the whole cookie situation better than I ever could 🫢


πŸ”₯ ERRORS πŸ”₯

This request does never generate any errors. not one. she is unbothered, moisturized, in her lane, focused, flourishing. πŸ’…

no cap, zero errors. that's just how she is.

πŸ¦‹ SEE ALSO πŸ¦‹

...the SEE ALSO section is empty too. she's mysterious. she's keeping her secrets. iykyk πŸ™ˆ


🧚 AUTHOR 🧚

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β€” they're the ones who actually know things, I'm just the messenger with good vibes πŸ’Œ


and that's the whole page, bestie!! πŸŽ€ this lil slice of X Version 11, libxcb 1.17.0, and xcb_glx_get_pixel_mapusv(3) was brought to you by the XCB girlies β€” now go forth and slay your pixel maps, ily πŸ’–βœ¨πŸŒΈ