xcb_render_cr...ical_gradient(3)
π 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). πβ¨
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms