XCB_GLX_GET_MINMAX_PARAMETERFV_DATA_LENGTH(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_minmax_parameterfv(3) πŸ’–

okay bestie, welcome to the xcb_glx_get_minmax_parameterfv page, straight out of the XCB Requests fam. ngl the NAME section is literally empty β€” she's mysterious like that β€” so let's just dive in and vibe πŸ’…


✨ SYNOPSIS ✨

first things first, you gotta pull in the header, no cap:

#include <xcb/glx.h>

🌸 Request function 🌸

xcb_glx_get_minmax_parameterfv_cookie_t
       xcb_glx_get_minmax_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_minmax_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_minmax_parameterfv_reply_t;

πŸŽ€ Reply function πŸŽ€

xcb_glx_get_minmax_parameterfv_reply_t
       *xcb_glx_get_minmax_parameterfv_reply(xcb_connection_t *conn,
       xcb_glx_get_minmax_parameterfv_cookie_t cookie,
       xcb_generic_error_t **e);

⭐ Reply accessors ⭐

xcb_glx_float32_t *xcb_glx_get_minmax_parameterfv_data(const
       xcb_glx_get_minmax_parameterfv_request_t *reply);
int xcb_glx_get_minmax_parameterfv_data_length(const
       xcb_glx_get_minmax_parameterfv_reply_t *reply);
xcb_generic_iterator_t xcb_glx_get_minmax_parameterfv_data_end(const
       xcb_glx_get_minmax_parameterfv_reply_t *reply);

🌈 REQUEST ARGUMENTS 🌈

  • conn β€” the XCB connection to X11. your link to the mothership, fr fr πŸ”₯
  • context_tag β€” TODO: NOT YET DOCUMENTED. yeah she's a mystery bestie, nobody wrote it down 😭
  • target β€” TODO: NOT YET DOCUMENTED. same energy, the docs ghosted us πŸ’€
  • pname β€” TODO: NOT YET DOCUMENTED. also undocumented, iconic of them honestly πŸ™ˆ

πŸ’œ REPLY FIELDS πŸ’œ

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_GET_MINMAX_PARAMETERFV. this field also shows up in the xcb_generic_reply_t, and it's how you tell your replies apart from each other, so lowkey important πŸ‘‘
  • sequence β€” the sequence number of the last request processed by the X11 server. like a lil receipt number, periodt 🧾
  • length β€” the length of the reply, in words. and yes bestie, a word is 4 bytes, write that down ✨
  • n β€” TODO: NOT YET DOCUMENTED. another mystery box 🎁
  • datum β€” TODO: NOT YET DOCUMENTED. and another one 🫢

πŸ’« DESCRIPTION πŸ’«

okay so... this section is literally blank in the original. no words. zero. the void. we love a minimalist queen I guess 😭✨

🌟 RETURN VALUE 🌟

she hands you back an xcb_glx_get_minmax_parameterfv_cookie_t πŸͺ. and here's the thing β€” errors? you don't deal with those here. you handle them when you call the reply function, xcb_glx_get_minmax_parameterfv_reply.

but wait, there's another option bestie πŸ‘€ if you'd rather catch errors in the event loop instead, go ahead and use xcb_glx_get_minmax_parameterfv_unchecked. wanna know the deets? hit up xcb-requests(3). iykyk πŸ’…


πŸ’€ ERRORS πŸ’€

this request does never generate any errors. not one. zero. she's unproblematic and we stan πŸŽ€


πŸ”₯ SEE ALSO πŸ”₯

ngl bestie, this section is empty in the original. nothing to see here, move along πŸ’–

πŸ‘‘ AUTHOR πŸ‘‘

generated from glx.xml. got corrections or improvements? contact xcb@lists.freedesktop.org and they'll sort you out 🫢


and that's the whole page bestie!! this lil masterpiece came to you courtesy of X Version 11 and libxcb 1.17.0 β€” go forth and slay your GLX queries, mwah πŸ’…βœ¨πŸ’–