xcb_randr_set_crtc_gamma(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_randr_set_crtc_gamma(3) πŸ’–

okay bestie, welcome to the XCB Requests corner of the manual, where we talk about xcb_randr_set_crtc_gamma. yes that's a whole mouthful, i know, but stick with me. 🫢


✨ NAME ✨

xcb_randr_set_crtc_gamma β€” and that's it. that's the whole description. the manpage literally left it blank, no cap. we're working with a mystery girl here. πŸ’€


✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/randr.h>

πŸŽ€ Request function πŸŽ€

here's the whole function, looking all cute and official:

xcb_void_cookie_t xcb_randr_set_crtc_gamma(xcb_connection_t *conn,
       xcb_randr_crtc_t crtc, uint16_t size, const uint16_t *red, const
       uint16_t *green, const uint16_t *blue);

✨ REQUEST ARGUMENTS ✨

okay so here's everyone in the cast, and i need you to brace yourself because the documentation for literally all of them is… nothing. πŸ™ˆ

  • conn β€” the XCB connection to X11. this one actually got documented, slay. it's your lil line to the X server, your main character connection. 🌈
  • crtc β€” TODO: NOT YET DOCUMENTED. yeah. that's the whole thing. iconic of them honestly. πŸ’…
  • size β€” TODO: NOT YET DOCUMENTED. again. no notes. πŸŽ€
  • red β€” TODO: NOT YET DOCUMENTED. the reds are mysterious. πŸ“
  • green β€” TODO: NOT YET DOCUMENTED. the greens are equally mysterious. 🌸
  • blue β€” TODO: NOT YET DOCUMENTED. and blue too. the whole rainbow is undocumented bestie. 😭

✨ DESCRIPTION ✨

so… there is no description. it's blank. empty. a void. the vibes are immaculate but the information is not present. i can't make up lore that isn't there, that would be lying to you and i would never. πŸ’œ


✨ RETURN VALUE ✨

this one hands you back an xcb_void_cookie_t. and because it's a void cookie, any errors (if any even show up) have to be handled over in the event loop. that's the deal. πŸ¦‹

but wait, there's an option. if you'd rather handle errors directly using xcb_request_check instead, then you want xcb_randr_set_crtc_gamma_checked. different function, same energy. go read xcb-requests(3) for the full tea. ⭐


✨ ERRORS ✨

good news bestie: this request does never generate any errors. she's low maintenance. she causes no drama. we love a peaceful queen. πŸ‘‘


✨ SEE ALSO ✨

nothing here either. no friends listed. she's a lone wolf. 🐺 (the xcb-requests(3) mention up in RETURN VALUE is the closest thing we get, iykyk.)


✨ AUTHOR ✨

this page was generated from randr.xml. if you spot something that needs correcting or improving, hit up xcb@lists.freedesktop.org β€” they're taking notes. πŸ“


and that's the whole page, babes. this beauty shipped with X Version 11 and libxcb 1.17.0. go forth and set some crtc gamma, whatever that ends up meaning. mwah. πŸ’‹βœ¨