xcb_render_tri_fan(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_tri_fan β€” the XCB Requests manual, bestie edition πŸŽ€

okay so real talk, this is xcb_render_tri_fan(3) from the XCB Requests crew, and she's a lil mysterious ngl (the NAME line literally has no description, iconic of her tbh). Let's get into it ✨


✨ NAME ✨

xcb_render_tri_fan β€” (the description slot is empty in the original, so we're keeping it empty, no cap 🫢)


🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header:

#include <xcb/render.h>

πŸ¦‹ Request function πŸ¦‹

here's the whole signature, bestie, copy it exactly πŸ’–:

xcb_void_cookie_t xcb_render_tri_fan(xcb_connection_t *conn, uint8_t op,
       xcb_render_picture_t src, xcb_render_picture_t dst,
       xcb_render_pictformat_t mask_format, int16_t src_x,
       int16_t src_y, uint32_t points_len, const
       xcb_render_pointfix_t *points);

like… look at her. nine arguments. main character energy fr fr πŸ‘‘


πŸŽ€ REQUEST ARGUMENTS πŸŽ€

  • conn β€” the XCB connection to X11. your lil hotline to the X server, she's the plug πŸ”Œ
  • op β€” TODO: NOT YET DOCUMENTED. (yes bestie, the docs literally say that, we're not making it up πŸ™ˆ)
  • src β€” TODO: NOT YET DOCUMENTED.
  • dst β€” TODO: NOT YET DOCUMENTED.
  • mask_format β€” TODO: NOT YET DOCUMENTED.
  • src_x β€” TODO: NOT YET DOCUMENTED.
  • src_y β€” TODO: NOT YET DOCUMENTED.
  • points_len β€” TODO: NOT YET DOCUMENTED.
  • points β€” TODO: NOT YET DOCUMENTED.
not me listing every single one even though they're all TODO 😭 the rule is we keep EVERYTHING, so here we are, slaying the completeness vibe check πŸ’…

🌈 DESCRIPTION 🌈

(okay so the DESCRIPTION section is genuinely empty in the original β€” she said "no thoughts, head empty" πŸ“ we're respecting that and not inventing lore. periodt.)


⭐ RETURN VALUE ⭐

She hands you back an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop. so like, you don't get them straight away, you gotta go vibe in the event loop and wait for them to show up 🌸

If you're the type who wants to deal with errors directly using xcb_request_check instead, then use xcb_render_tri_fan_checked. peek xcb-requests(3) for the deets πŸ‘‘


πŸ’€ ERRORS πŸ’€

ngl this one's chill: this request does never generate any errors. zero drama, zero chaos, she's unbothered πŸ’–


🫢 SEE ALSO 🫢

(nothing listed here in the original β€” the section exists, the content said "not today" πŸ™ˆ)


🌟 AUTHOR 🌟

Generated from render.xml. For corrections and improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who actually know things πŸ’Œ


and that's the whole page bestie!! πŸŽ€πŸ’– this came from X Version 11, libxcb 1.17.0 β€” shoutout to the libxcb 1.17.0 girlies, and yeah, that's the xcb_render_tri_fan(3) footer energy, we said it, we meant it, bye bestieee πŸ¦‹βœ¨πŸ’