xcb_glx_get_histogram(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_histogram ✨

okay bestie, welcome to the manual page for xcb_glx_get_histogram, a little request from the XCB Requests family (that's the manual section, iykyk). it lives in the glx world, it's giving "ask the X server for a histogram and get a cookie back" energy, and we're gonna walk through it together. no gatekeeping. πŸ’–


🌸 NAME 🌸

xcb_glx_get_histogram β€” no description was ever written here, bestie, the manpage just leaves it blank and honestly? iconic of it


πŸ¦‹ SYNOPSIS πŸ¦‹

First, include the header. you know the drill:

#include <xcb/glx.h>

πŸ’… Request function

xcb_glx_get_histogram_cookie_t
       xcb_glx_get_histogram(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t target,
       uint32_t format, uint32_t type, uint8_t swap_bytes,
       uint8_t reset);

πŸŽ€ Reply datastructure

typedef struct xcb_glx_get_histogram_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad1[8];
    int32_t  width;
    uint8_t  pad2[12];
} xcb_glx_get_histogram_reply_t;

✨ Reply function

xcb_glx_get_histogram_reply_t
       *xcb_glx_get_histogram_reply(xcb_connection_t *conn,
       xcb_glx_get_histogram_cookie_t cookie, xcb_generic_error_t **e);

🧚 Reply accessors

uint8_t *xcb_glx_get_histogram_data(const
       xcb_glx_get_histogram_request_t *reply);

int xcb_glx_get_histogram_data_length(const
       xcb_glx_get_histogram_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_histogram_data_end(const
       xcb_glx_get_histogram_reply_t *reply);

πŸ’œ REQUEST ARGUMENTS πŸ’œ

  • conn β€” your XCB connection to X11. your whole link to the server, your ride or die. 🫢
  • context_tag β€” TODO: NOT YET DOCUMENTED. literally the manpage says nothing, bestie, we're all just vibing
  • target β€” TODO: NOT YET DOCUMENTED.
  • format β€” TODO: NOT YET DOCUMENTED.
  • type β€” TODO: NOT YET DOCUMENTED.
  • swap_bytes β€” TODO: NOT YET DOCUMENTED.
  • reset β€” TODO: NOT YET DOCUMENTED.

🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_GET_HISTOGRAM. this field is also chillin' in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. very "how do you do, fellow replies" of it. 😭
  • sequence β€” the sequence number of the last request the X11 server processed. the receipts, basically.
  • length β€” how long the reply is, in words. and just so we're clear: a word is 4 bytes. periodt.
  • width β€” TODO: NOT YET DOCUMENTED.

πŸ“ DESCRIPTION πŸ“

there is literally nothing here. the section exists, it's empty, it's serving minimalism. we move.


πŸ’– RETURN VALUE πŸ’–

Returns an xcb_glx_get_histogram_cookie_t. πŸͺ

Errors have to be handled when you call the reply function, xcb_glx_get_histogram_reply.

If you'd rather handle errors in the event loop instead, use xcb_glx_get_histogram_unchecked. See xcb-requests(3) for the deets.


πŸ”₯ ERRORS πŸ”₯

this request does never generate any errors. not one. zero. clean sheet. slay. πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

(nothing listed here, bestie β€” the section is there but it's empty, we respect the silence)


🌟 AUTHOR 🌟

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 🫢


and that's the whole page, babe. this was X Version 11, libxcb 1.17.0, and it's the xcb_glx_get_histogram(3) manual. go forth and get those histograms. bye bestie! πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈ