xcb_glx_get_mapdv(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_mapdv β€” bestie edition

okay so like, this is xcb_glx_get_mapdv, a lil request from the XCB Requests fam, living over in libxcb. It's giving "glx, but make it a network round-trip." Let's get into it 🫢


✨ NAME ✨

xcb_glx_get_mapdv β€” no cap, that's the whole name, the original page literally just left it hanging there with a lil dash and zero explanation πŸ’€ so we move.


🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header or nothing works:

#include <xcb/glx.h>

πŸŽ€ Request function

xcb_glx_get_mapdv_cookie_t xcb_glx_get_mapdv(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t target,
       uint32_t query);

πŸ¦‹ Reply datastructure

typedef struct xcb_glx_get_mapdv_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_mapdv_reply_t;

🧚 Reply function

xcb_glx_get_mapdv_reply_t
       *xcb_glx_get_mapdv_reply(xcb_connection_t *conn,
       xcb_glx_get_mapdv_cookie_t cookie, xcb_generic_error_t **e);

⭐ Reply accessors

xcb_glx_float64_t *xcb_glx_get_mapdv_data(const
       xcb_glx_get_mapdv_request_t *reply);

int xcb_glx_get_mapdv_data_length(const xcb_glx_get_mapdv_reply_t
       *reply);

xcb_generic_iterator_t xcb_glx_get_mapdv_data_end(const
       xcb_glx_get_mapdv_reply_t *reply);

πŸ‘‘ REQUEST ARGUMENTS πŸ‘‘

  • conn β€” the XCB connection to X11, your lil hotline to the server πŸ’–
  • context_tag β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "not today" πŸ™ˆ
  • target β€” TODO: NOT YET DOCUMENTED. also a mystery, also iconic πŸ’…
  • query β€” TODO: NOT YET DOCUMENTED. the third mystery sibling, slay ✨

🌈 REPLY FIELDS 🌈

  • response_type β€” the type of this reply, which in this case is XCB_GLX_GET_MAPDV. This field is also chilling in the xcb_generic_reply_t and you can use it to tell replies apart from each other, so it's basically the name tag at the party πŸŽ€
  • 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, periodt) πŸ”₯
  • n β€” TODO: NOT YET DOCUMENTED. mysterious. lowkey obsessed 😭
  • datum β€” TODO: NOT YET DOCUMENTED. the mystery continues, fr fr πŸ¦‹

πŸ’œ DESCRIPTION πŸ’œ

the original page's DESCRIPTION section is, and I cannot stress this enough, empty. absolutely nothing. a void. a blank canvas. not me reading it three times to make sure πŸ’€

so like, there's nothing to describe here, bestie. the vibes are simply unspecified. we respect it.


πŸ’– RETURN VALUE πŸ’–

It hands you back an xcb_glx_get_mapdv_cookie_t πŸ“ β€” yes, a cookie, because XCB loves a snack-themed type name. Errors have to be handled when calling the reply function xcb_glx_get_mapdv_reply.

If you'd rather handle errors in the event loop instead, use xcb_glx_get_mapdv_unchecked. See xcb-requests(3) for the deets πŸ‘€


πŸ’€ ERRORS πŸ’€

This request does never generate any errors.

like, at all. zero. none. the drama-free queen of requests πŸ‘‘βœ¨


🫢 SEE ALSO 🫢

(nothing listed here in the original β€” it's a vibe-only section, and we're keeping it that way πŸ’…)

🌸 AUTHOR 🌸

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


and that's the whole thing, bestie!! this page came to you from X Version 11, libxcb 1.17.0, on the date stamped right there in the footer of xcb_glx_get_mapdv(3) πŸŽ€ mwah, go forth and call your requests, ily πŸ¦‹πŸ’–βœ¨