xcb_render_cr...ical_gradient(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

πŸ’… NAME πŸ’…

xcb_render_create_conical_gradient β€” okay bestie, the title of this whole thing is xcb_render_cr...ical_gradient(3), and it lives in the XCB Requests section of the manual. The name itself is short and mysterious and honestly kind of giving "no further notes" energy.


✨ SYNOPSIS ✨

First things first, you gotta pull in the header:

#include <xcb/render.h>

πŸŽ€ Request function πŸŽ€

xcb_void_cookie_t
       xcb_render_create_conical_gradient(xcb_connection_t *conn,
       xcb_render_picture_t picture, xcb_render_pointfix_t center,
       xcb_render_fixed_t angle, uint32_t num_stops, const
       xcb_render_fixed_t *stops, const xcb_render_color_t *colors);

That's the whole vibe. Seven arguments, one cookie, zero drama (allegedly).


🫢 REQUEST ARGUMENTS 🫢

  • conn β€” the XCB connection to X11. Your little lifeline to the server, periodt.
  • picture β€” TODO: NOT YET DOCUMENTED. Bestie... the docs really said "figure it out" 😭
  • center β€” TODO: NOT YET DOCUMENTED. Same energy, different argument.
  • angle β€” TODO: NOT YET DOCUMENTED. The mystery continues.
  • num_stops β€” TODO: NOT YET DOCUMENTED. Still nothing. Not a crumb.
  • stops β€” TODO: NOT YET DOCUMENTED. Iconic in its emptiness honestly.
  • colors β€” TODO: NOT YET DOCUMENTED. And that's the whole list, no notes.
ngl, that's a LOT of TODO up in here. We're all just out here rawdogging the upstream docs together. πŸ’€

🌸 DESCRIPTION 🌸

Okay so here's the thing β€” there is literally nothing here. The DESCRIPTION section of the original is blank. Empty. Void-coded. The way that it says absolutely nothing is honestly kind of a serve, but like... it's also just empty, bestie. That's it. That's the section. πŸ™ˆ


πŸ‘‘ RETURN VALUE πŸ‘‘

It hands you back an xcb_void_cookie_t. And here's the important part, so listen up: errors (if any) have to be handled in the event loop. That's not optional, that's the assignment. 🫑

If you'd rather handle errors directly with xcb_request_check instead, then you want xcb_render_create_conical_gradient_checked β€” the checked twin, the responsible sibling, the one who does their homework. See xcb-requests(3) for all the details, fr fr.


πŸ’– ERRORS πŸ’–

This request does never generate any errors.

Read that again. Zero. None. Not one. It's giving immaculate behavior. ✨ No error handling arc for you here, bestie β€” this one is chill like that.


πŸ¦‹ SEE ALSO πŸ¦‹

...nothing. Genuinely nothing listed here. The section is there, it just has no friends. Not a single cross-reference. A true solo act. πŸ’…


🌈 AUTHOR 🌈

Generated from render.xml. If you wanna send corrections and improvements, contact xcb@lists.freedesktop.org β€” they're literally asking, so don't be shy. 🫢


Okay bestie, that's the whole page β€” you read the entire thing, you absolute legend. 🌟 This little doc came to you courtesy of X Version 11 and libxcb 1.17.0, and that's the tea. Sip responsibly, slay responsibly, and go make some conical gradients (or at least pass the right arguments). πŸ’œβœ¨