XCB_GLX_GET_CONVOLUTION_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_convolution_parameterfv(3) 🌸

okay bestie, welcome to the XCB Requests section of the manual, and today's main character is xcb_glx_get_convolution_parameterfv πŸ’…


✨ NAME ✨

xcb_glx_get_convolution_parameterfv β€” that's literally it, the manpage gives us no one-liner, so we're keeping it mysterious πŸ™ˆ


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <xcb/glx.h>

πŸ’– Request function πŸ’–

xcb_glx_get_convolution_parameterfv_cookie_t
       xcb_glx_get_convolution_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_convolution_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_convolution_parameterfv_reply_t;

🌈 Reply function 🌈

xcb_glx_get_convolution_parameterfv_reply_t
       *xcb_glx_get_convolution_parameterfv_reply(xcb_connection_t *conn,
       xcb_glx_get_convolution_parameterfv_cookie_t cookie,
       xcb_generic_error_t **e);

⭐ Reply accessors ⭐

xcb_glx_float32_t *xcb_glx_get_convolution_parameterfv_data(const
       xcb_glx_get_convolution_parameterfv_request_t *reply);
int xcb_glx_get_convolution_parameterfv_data_length(const
       xcb_glx_get_convolution_parameterfv_reply_t *reply);
xcb_generic_iterator_t
       xcb_glx_get_convolution_parameterfv_data_end(const
       xcb_glx_get_convolution_parameterfv_reply_t *reply);

πŸ’œ REQUEST ARGUMENTS πŸ’œ

  • conn β€” the XCB connection to X11, obvi. it's giving "your link to the server" energy πŸ”₯
  • context_tag β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "no thoughts, head empty" 😭
  • target β€” TODO: NOT YET DOCUMENTED. also a mystery fr fr
  • pname β€” TODO: NOT YET DOCUMENTED. the trilogy of unknowns, iconic honestly πŸ™ˆ

🧚 REPLY FIELDS 🧚

  • response_type β€” the type of this reply, which in this case is XCB_GLX_GET_CONVOLUTION_PARAMETERFV. this field also lives in the xcb_generic_reply_t, so you can use it to tell replies apart from each other, like a little name tag at a party πŸŽ€
  • sequence β€” the sequence number of the last request processed by the X11 server. lowkey your receipt number 🧾
  • length β€” the length of the reply, in words (a word is 4 bytes). so, math, but make it X11 πŸ’…
  • n β€” TODO: NOT YET DOCUMENTED. we simply do not know her 🫢
  • datum β€” TODO: NOT YET DOCUMENTED. same, bestie, same 😭

🌸 DESCRIPTION 🌸

…and that's it. that's the description. the manpage left this section completely empty, so there is literally nothing documented here. not me staring at a blank section πŸ’€


πŸ”₯ RETURN VALUE πŸ”₯

Returns an xcb_glx_get_convolution_parameterfv_cookie_t. Errors have to be handled when calling the reply function xcb_glx_get_convolution_parameterfv_reply.

If you want to handle errors in the event loop instead, use xcb_glx_get_convolution_parameterfv_unchecked. See xcb-requests(3) for details.

so like β€” the cookie is your little "i'll be back for the actual answer" token, and errors? not the function's problem at call time, you deal with them at reply time. periodt πŸ’…

πŸ’€ ERRORS πŸ’€

This request does never generate any errors.

literally never. zero. none. she's unproblematic ✨

πŸ¦‹ SEE ALSO πŸ¦‹

nothing listed here β€” the section exists but it's empty, so there's no cross-reference to chase. πŸŽ€


πŸ‘‘ AUTHOR πŸ‘‘

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

shoutout to the XML generator for doing the heavy lifting 🫢 and yes, if something's wrong, that's the email, bestie πŸ“§

and that's the whole page, no cap. you read every single field, every TODO, every pad byte, and you ate πŸ’…

signing off from X Version 11, libxcb 1.17.0 β€” stay slay, stay linked, and always check your reply fields 🌈✨