xcb_glx_pixel_storei(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_pixel_storei 💅

okay bestie, welcome to xcb_glx_pixel_storei from the <xcb/glx.h> cinematic universe (manual section 3, XCB Requests, if we're being official about it). it's a GLX request function, it exists, and we're gonna talk about it. 🦋

✨ NAME ✨

xcb_glx_pixel_storei — and honestly? that's it. that's the whole name. the original page leaves the description blank, so I'm not gonna sit here and make up lore. no cap, the name is just the name. 💀

🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/glx.h>

🎀 Request function 🎀

here's the signature, copy it exactly, don't freestyle:

xcb_void_cookie_t xcb_glx_pixel_storei(xcb_connection_t *conn,
       xcb_glx_context_tag_t context_tag, uint32_t pname,
       int32_t datum);

👑 REQUEST ARGUMENTS 👑

four args, four little icons, let's go:

  • conn — your XCB connection to X11. the whole line to the server, your main character connection. 🔥
  • context_tag — literally marked TODO: NOT YET DOCUMENTED. in the source. so... yeah. we don't know. neither does the manpage. we're all in the dark together and that's valid. 🙈
  • pname — also TODO: NOT YET DOCUMENTED. bestie I cannot make something up, that would be lying to you and I would never. 😭
  • datum — you guessed it: TODO: NOT YET DOCUMENTED. three for three. iconic honestly. ✨
not me having nothing to tell you about three of the four arguments. the manpage said "TODO" and I respect the honesty. 🫶

🌈 DESCRIPTION 🌈

so the DESCRIPTION section on this page is... empty. completely empty. it's giving minimalist. it's giving mystery. it's giving "the docs are still cooking." nothing here to report, bestie, and I refuse to invent behavior that isn't documented. ⭐

💜 RETURN VALUE 💜

it hands you back an xcb_void_cookie_t. that's the whole vibe. and here's the important part:

  • errors (if there are any) have to be handled in the event loop. that's the rule. that's where you deal with them.
  • if you'd rather handle errors directly with xcb_request_check instead, then use xcb_glx_pixel_storei_checked. that's the checked version, that's your girl for direct error handling.
  • see xcb-requests(3) for the details, because that page is the one that actually explains the cookie situation. 🍓

💀 ERRORS 💀

good news era: this request does never generate any errors. no error codes, no drama, no nothing. flawless behavior. we love a low-maintenance request. 💅

🧚 SEE ALSO 🧚

this section is empty on the original page. nothing linked, nothing referenced. so there's nothing for me to send you to, and I'm not about to make up a cross-reference. the void is the cross-reference. ✨

🫶 AUTHOR 🫶

generated from glx.xml. if you want corrections or improvements, hit up xcb@lists.freedesktop.org — that's the address, that's who to email, don't shoot the messenger. 💌

okay so final vibe check, bestie: this page is X Version 11, libxcb 1.17.0, and it lives at xcb_glx_pixel_storei(3). thanks for reading the whole thing, you ate that. now go handle your errors in the event loop like the icon you are. periodt. 👑💖

📦 where this page comes from