xcb_glx_get_tex_parameterfv(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_tex_parameterfv β€” ok bestie, let's talk

so this is a page from XCB Requests, living in the libxcb fam, and it's literally called xcb_glx_get_tex_parameterfv(3). it's the GLX "hey X server, tell me about this texture parameter" request. no cap, that's the whole vibe.


✨ NAME ✨

xcb_glx_get_tex_parameterfv β€” and that's it, that's the name, the manpage itself left it blank after the dash so we're all just out here vibing πŸ™ˆ


🌸 SYNOPSIS 🌸

first things first, you gotta invite the header in:

#include <xcb/glx.h>

πŸŽ€ Request function

xcb_glx_get_tex_parameterfv_cookie_t
xcb_glx_get_tex_parameterfv(xcb_connection_t *conn,
                            xcb_glx_context_tag_t context_tag,
                            uint32_t target,
                            uint32_t pname);

πŸ¦‹ Reply datastructure

the lil glow-up struct you get back:

typedef struct xcb_glx_get_tex_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_tex_parameterfv_reply_t;

πŸ’– Reply function

xcb_glx_get_tex_parameterfv_reply_t *
xcb_glx_get_tex_parameterfv_reply(xcb_connection_t *conn,
                                  xcb_glx_get_tex_parameterfv_cookie_t cookie,
                                  xcb_generic_error_t **e);

🌈 Reply accessors

these are the little helpers that dig through the reply for you:

xcb_glx_float32_t *xcb_glx_get_tex_parameterfv_data(const xcb_glx_get_tex_parameterfv_request_t *reply);

int xcb_glx_get_tex_parameterfv_data_length(const xcb_glx_get_tex_parameterfv_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_tex_parameterfv_data_end(const xcb_glx_get_tex_parameterfv_reply_t *reply);
πŸ‘€ psst β€” yes, xcb_glx_get_tex_parameterfv_data really does take an xcb_glx_get_tex_parameterfv_request_t * up there, not a reply. that's what the page says, so that's what we're saying. character for character, bestie.

πŸ”₯ REQUEST ARGUMENTS πŸ”₯

  • conn β€” your XCB connection to X11. the whole group chat, basically.
  • context_tag β€” TODO: NOT YET DOCUMENTED. literally the manpage's own words, i'm not gonna make stuff up for you πŸ’€
  • target β€” TODO: NOT YET DOCUMENTED. same energy.
  • pname β€” TODO: NOT YET DOCUMENTED. yep. all three of them. we move.

πŸ‘‘ REPLY FIELDS πŸ‘‘

  • response_type β€” the type of this reply, and in this specific case it's XCB_GLX_GET_TEX_PARAMETERFV. this field also lives inside the xcb_generic_reply_t, and you can use it to tell your replies apart from each other. it's giving name-tag at a party 🏷️
  • sequence β€” the sequence number of the last request processed by the X11 server. the receipts, fr fr.
  • length β€” how long the reply is, in words (and a word here is 4 bytes, keep that in your notes).
  • n β€” TODO: NOT YET DOCUMENTED.
  • datum β€” TODO: NOT YET DOCUMENTED.

πŸ’œ DESCRIPTION πŸ’œ

so the DESCRIPTION section on this page is... empty. nothing. a void. the manpage said "no thoughts, head empty" and honestly? respect 🫢 we are not adding lore that isn't there.


⭐ RETURN VALUE ⭐

you get back an xcb_glx_get_tex_parameterfv_cookie_t. it's a cookie πŸͺ and like all good cookies, it's a promise of something delicious later.

errors? those have to be handled when you call the reply function xcb_glx_get_tex_parameterfv_reply.

but if you'd rather handle your errors in the event loop instead, use xcb_glx_get_tex_parameterfv_unchecked. see xcb-requests(3) for the details on that whole situation.


πŸ’€ ERRORS πŸ’€

good news, icon behavior: this request does never generate any errors. zero. none. a clean queen ✨


🧚 SEE ALSO 🧚

(also empty. they really just left it there like a decorative plant 🌱)


🌸 AUTHOR 🌸

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


okay that's the whole page, you ate it, no crumbs left πŸ’…βœ¨ stay hydrated, keep your pad fields in check, and remember: pad0, pad1[4], pad2[12] are all just there so the struct sits pretty β€” that's on alignment, not on you, bestie 🫢

and for the sign-off: this lil masterpiece is X Version 11, libxcb 1.17.0, filed under xcb_glx_get_tex_parameterfv(3). slay, mwah 😘