XCB_GLX_GET_HISTOGRAM_PARAMETERFV_REPLY(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_parameterfv(3) πŸ’–

okay so bestie, this is a page from the XCB Requests corner of the libxcb manual, and it's all about xcb_glx_get_histogram_parameterfv. yeah that name is a mouthful, we're saying it with our whole chest anyway. 🫢


✨ NAME ✨

xcb_glx_get_histogram_parameterfv β€” and honestly that's the whole name, the original just leaves it hanging there with a lil dash, iconic honestly. πŸ’…


🌈 SYNOPSIS 🌈

first up, the include, don't forget her:

#include <xcb/glx.h>

πŸŽ€ Request function πŸŽ€

xcb_glx_get_histogram_parameterfv_cookie_t
       xcb_glx_get_histogram_parameterfv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t target,
       uint32_t pname);

πŸ¦‹ Reply datastructure πŸ¦‹

typedef struct xcb_glx_get_histogram_parameterfv_reply_t {
    uint8_t           response_type;
    uint8_t           pad0;
    uint16_t          sequence;
    uint32_t          length;
    uint8_t           pad1[4];
    uint32_t          n;
    xcb_glx_float32_t datum;
    uint8_t           pad2[12];
} xcb_glx_get_histogram_parameterfv_reply_t;

πŸ“ Reply function πŸ“

xcb_glx_get_histogram_parameterfv_reply_t
       *xcb_glx_get_histogram_parameterfv_reply(xcb_connection_t *conn,
       xcb_glx_get_histogram_parameterfv_cookie_t cookie,
       xcb_generic_error_t **e);

πŸ’œ Reply accessors πŸ’œ

xcb_glx_float32_t *xcb_glx_get_histogram_parameterfv_data(const
       xcb_glx_get_histogram_parameterfv_request_t *reply);

int xcb_glx_get_histogram_parameterfv_data_length(const
       xcb_glx_get_histogram_parameterfv_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_histogram_parameterfv_data_end(const
       xcb_glx_get_histogram_parameterfv_reply_t *reply);
not me triple-checking that the first accessor really says ..._request_t and not ..._reply_t β€” yeah bestie, it does, and we are transcribing it character for character, no edits, that's the assignment. πŸ™ˆ

🌸 REQUEST ARGUMENTS 🌸

  • conn β€” the XCB connection to X11. your lil hotline to the server, she's the main character here. πŸ‘‘
  • context_tag β€” TODO: NOT YET DOCUMENTED. literally the docs said "idk yet" and we respect the honesty. πŸ’€
  • target β€” TODO: NOT YET DOCUMENTED.
  • pname β€” TODO: NOT YET DOCUMENTED.

⭐ REPLY FIELDS ⭐

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_GET_HISTOGRAM_PARAMETERFV. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. vibe check your packets, bestie. πŸ”₯
  • sequence β€” the sequence number of the last request processed by the X11 server.
  • length β€” the length of the reply, in words. and a word is 4 bytes, no cap. πŸ“
  • n β€” TODO: NOT YET DOCUMENTED.
  • datum β€” TODO: NOT YET DOCUMENTED.

🧚 DESCRIPTION 🧚

okay so… there is literally nothing here. the section exists, it's just empty. she's giving mystery, she's giving silence, she's giving "the real description was the friends we made along the way". πŸ’€βœ¨


πŸ’… RETURN VALUE πŸ’…

Returns an xcb_glx_get_histogram_parameterfv_cookie_t. πŸͺ

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

If you'd rather handle errors in the event loop instead, use xcb_glx_get_histogram_parameterfv_unchecked. see xcb-requests(3) for details.


🚨 ERRORS 🚨

This request does never generate any errors. clean. spotless. zero drama. the icon behavior honestly. 😌

πŸ‘€ SEE ALSO πŸ‘€

nothing listed here bestie, it's a blank space, we love a minimalist moment. 🌈


πŸ’– AUTHOR πŸ’–

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


that's the whole page, bestie, go forth and request your histogram parameterfv πŸ¦‹

X Version 11 Β· libxcb 1.17.0 Β· mwah, love u, bye πŸ’‹