xcb_glx_get_polygon_stipple(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_polygon_stipple ✨

okay bestie, so this one lives in the XCB requests crew, specifically the GLX corner of it — that's xcb_glx_get_polygon_stipple, from the <xcb/glx.h> header. it's giving "ask the X server what the polygon stipple looks like rn" energy 💅

🌸 NAME 🌸

xcb_glx_get_polygon_stipple -

(yeah the original leaves it blank after the dash, no cap, that's literally how it ships 🙈)

🦋 SYNOPSIS 🦋

#include <xcb/glx.h>

💖 Request function 💖

xcb_glx_get_polygon_stipple_cookie_t
       xcb_glx_get_polygon_stipple(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint8_t lsb_first);

💖 Reply datastructure 💖

typedef struct xcb_glx_get_polygon_stipple_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint8_t  pad1[24];
} xcb_glx_get_polygon_stipple_reply_t;

💖 Reply function 💖

xcb_glx_get_polygon_stipple_reply_t
       *xcb_glx_get_polygon_stipple_reply(xcb_connection_t *conn,
       xcb_glx_get_polygon_stipple_cookie_t cookie,
       xcb_generic_error_t **e);

💖 Reply accessors 💖

uint8_t *xcb_glx_get_polygon_stipple_data(const
       xcb_glx_get_polygon_stipple_request_t *reply);

int xcb_glx_get_polygon_stipple_data_length(const
       xcb_glx_get_polygon_stipple_reply_t *reply);

xcb_generic_iterator_t xcb_glx_get_polygon_stipple_data_end(const
       xcb_glx_get_polygon_stipple_reply_t *reply);

🎀 REQUEST ARGUMENTS 🎀

  • conn — the XCB connection to X11. your lil hotline to the server fr fr ☎️
  • context_tag — TODO: NOT YET DOCUMENTED. (the docs said "idk yet" and honestly? iconic of them 😭)
  • lsb_first — TODO: NOT YET DOCUMENTED. (same vibe, same mystery 🕵️♀️)

🌈 REPLY FIELDS 🌈

  • response_type — the type of this reply, and in this case it's XCB_GLX_GET_POLYGON_STIPPLE. this field also shows up in the xcb_generic_reply_t, so you can use it to tell replies apart from each other. it's the "which one are you" field bestie 👑
  • sequence — the sequence number of the last request processed by the X11 server. lowkey the server's little receipt number 🧾
  • length — the length of the reply, in words (and a word is 4 bytes, periodt).

✨ DESCRIPTION ✨

(empty. nothing. void. the original just… doesn't say anything here, and we respect the silence 💀)

💜 RETURN VALUE 💜

Returns an xcb_glx_get_polygon_stipple_cookie_t. Errors have to be handled when calling the reply function xcb_glx_get_polygon_stipple_reply. so like, don't forget your error handling bestie, that's main character behavior 🫶

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

🔥 ERRORS 🔥

This request does never generate any errors. not a single one. zero. flawless. ate and left no crumbs 💅

🍓 SEE ALSO 🍓

(nothing listed here — the section is there but it's empty, and that's just how it is 🙈)

🧚 AUTHOR 🧚

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

heads up bestie: context_tag and lsb_first are marked TODO: NOT YET DOCUMENTED in the original, so i'm not gonna make up what they do — no cap, i'm not inventing facts for you 💖

okay that's the whole page!! this was generated for X Version 11, libxcb 1.17.0, and it's the xcb_glx_get_polygon_stipple(3) moment. mwah, bye bestie 😘💖✨

📦 where this page comes from