xcb_glx_get_doublev(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_doublev πŸ’–

okay so bestie, welcome to the xcb_glx_get_doublev page from the XCB Requests manual set. yes it's a real manpage, yes it's from libxcb, and yes we're gonna make it make sense. πŸ¦‹


✨ NAME ✨

xcb_glx_get_doublev β€” no description given, the original page literally just vibes here πŸ™ˆ


✨ SYNOPSIS ✨

#include <xcb/glx.h>

πŸŽ€ Request function

xcb_glx_get_doublev_cookie_t xcb_glx_get_doublev(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t pname);

πŸŽ€ Reply datastructure

typedef struct xcb_glx_get_doublev_reply_t {
    uint8_t           response_type;
    uint8_t           pad0;
    uint16_t          sequence;
    uint32_t          length;
    uint8_t           pad1[4];
    uint32_t          n;
    xcb_glx_float64_t datum;
    uint8_t           pad2[8];
} xcb_glx_get_doublev_reply_t;

πŸŽ€ Reply function

xcb_glx_get_doublev_reply_t
       *xcb_glx_get_doublev_reply(xcb_connection_t *conn,
       xcb_glx_get_doublev_cookie_t cookie, xcb_generic_error_t **e);

πŸŽ€ Reply accessors

xcb_glx_float64_t *xcb_glx_get_doublev_data(const
       xcb_glx_get_doublev_request_t *reply);

int xcb_glx_get_doublev_data_length(const xcb_glx_get_doublev_reply_t
       *reply);

xcb_generic_iterator_t xcb_glx_get_doublev_data_end(const
       xcb_glx_get_doublev_reply_t *reply);

✨ REQUEST ARGUMENTS ✨

  • conn β€” the XCB connection to X11. your lil hotline to the server, she's the main character fr πŸ’…
  • context_tag β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs simply did not show up to class that day 😭
  • pname β€” TODO: NOT YET DOCUMENTED. same energy. not a single word. iconic honestly πŸ’€

✨ REPLY FIELDS ✨

  • response_type β€” the type of this reply, and in this case it's XCB_GLX_GET_DOUBLEV. this field also lives in the xcb_generic_reply_t, so 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. receipts, basically.
  • length β€” the length of the reply, in words. and no, not vibes-words β€” a word here is 4 bytes. πŸ“
  • n β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ
  • datum β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ

✨ DESCRIPTION ✨

literally nothing here bestie, the section exists and that's the whole personality. 🌸


✨ RETURN VALUE ✨

Returns an xcb_glx_get_doublev_cookie_t. πŸͺ

heads up: errors have to be handled when you call the reply function xcb_glx_get_doublev_reply.

If you'd rather handle errors in the event loop instead, use xcb_glx_get_doublev_unchecked. see xcb-requests(3) for the deets. no cap. 🫢


✨ ERRORS ✨

This request does never generate any errors. zero drama, zero chaos, we love a peaceful queen πŸ‘‘


✨ SEE ALSO ✨

<nothing listed on the original page, bestie β€” this section is serving empty-plate-at-a-party energy> 🍽️


✨ AUTHOR ✨

Generated from glx.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. πŸ“¬


and that's the whole page, bestie!! πŸ’œ this one came from X Version 11, libxcb 1.17.0, and it's filed under xcb_glx_get_doublev(3) β€” mwah, go forth and query your doubles responsibly βœ¨πŸŽ€πŸ¦‹