XCB_RENDER_CREATE_LINEAR_GRADIENT_CHECKED(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_render_create_linear_gradient β€” from the XCB Requests manual ✨

okay bestie, welcome to the glow-up manual for xcb_render_create_linear_gradient, straight outta the XCB Requests section. it's giving "let's make a gradient and make it linear" πŸ’…


🌈 NAME 🌈

xcb_render_create_linear_gradient -

(yes, that's it. the original is literally just a dash. the NAME section said nothing else, and I'm not about to invent lore. iconic minimalism, honestly πŸŽ€)


✨ SYNOPSIS ✨

#include <xcb/render.h>

Request function

xcb_void_cookie_t
       xcb_render_create_linear_gradient(xcb_connection_t *conn,
       xcb_render_picture_t picture, xcb_render_pointfix_t p1,
       xcb_render_pointfix_t p2, uint32_t num_stops, const
       xcb_render_fixed_t *stops, const xcb_render_color_t *colors);

like. look at that signature. seven whole arguments. she's high maintenance and she's worth it 🫢


πŸŽ€ REQUEST ARGUMENTS πŸŽ€

  • conn β€” the XCB connection to X11. your link to the mothership, your group chat with the X server, your whole entire situationship with display πŸ’–
  • picture β€” TODO: NOT YET DOCUMENTED. (the docs really said "no thoughts, head empty" on this one 😭)
  • p1 β€” TODO: NOT YET DOCUMENTED.
  • p2 β€” TODO: NOT YET DOCUMENTED.
  • num_stops β€” TODO: NOT YET DOCUMENTED.
  • stops β€” TODO: NOT YET DOCUMENTED.
  • colors β€” TODO: NOT YET DOCUMENTED.
ngl bestie, the upstream docs left these as blank as my weekend plans. I'm keeping them exactly as-is because making stuff up is not the vibe. 🚫 no cap.

πŸ’œ DESCRIPTION πŸ’œ

...and that's it. the DESCRIPTION section is empty. literally nothing. an absolute void. the silence is deafening πŸ”₯

we move. periodt.


⭐ RETURN VALUE ⭐

Returns an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop.

If you want to handle errors directly with xcb_request_check instead, use xcb_render_create_linear_gradient_checked. See xcb-requests(3) for details.

so like, the cookie is your little receipt πŸͺ and if something goes wrong you find out later in the event loop, not right away. if you're the impatient type (same, bestie πŸ™ˆ) then grab the _checked version and yell at it directly. the full tea is in xcb-requests(3).


πŸ’€ ERRORS πŸ’€

This request does never generate any errors.

zero drama. no errors. she's unbothered, moisturized, in her lane, thriving. πŸ‘‘


🌸 SEE ALSO 🌸

(the original SEE ALSO section is empty β€” nothing listed. so there's nothing to link here, and I'm not gonna manifest references out of thin air ✨)


πŸ¦‹ AUTHOR πŸ¦‹

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

like, if something's wrong, tell the list. they're the ones who actually wrote it, I'm just the messenger with better vibes πŸ’Œ


okay that's the whole page bestie, thanks for reading my lil manual rant πŸ«ΆπŸ’–

this was X Version 11, libxcb 1.17.0 β€” slay, mwah, bye πŸŽ€βœ¨