xcb_poly_fill_arc(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_poly_fill_arc β€” bestie edition πŸŽ€

okay so welcome to the xcb_poly_fill_arc(3) page, part of the XCB Requests crew ✨


✨ NAME ✨

xcb_poly_fill_arc β€” and honestly? that's it. The original page leaves the description blank after the dash, so we're matching energy. It's giving mystery. It's giving "figure it out yourself, girl." 🫢


🌸 SYNOPSIS 🌸

First things first, you gotta bring in the header, no cap:

#include <xcb/xproto.h>

πŸ¦‹ Request function

here's the whole vibe, character for character:

xcb_void_cookie_t xcb_poly_fill_arc(xcb_connection_t *conn,
       xcb_drawable_t drawable, xcb_gcontext_t gc, uint32_t arcs_len,
       const xcb_arc_t *arcs);

πŸ’– REQUEST ARGUMENTS πŸ’–

  • conn β€” The XCB connection to X11. Your lil hotline to the server, periodt.
  • drawable β€” TODO: NOT YET DOCUMENTED. yeah. The manpage literally says that. Not me being lazy, that's just canon 😭
  • gc β€” TODO: NOT YET DOCUMENTED. same situation, bestie. Iconic of the docs honestly.
  • arcs_len β€” TODO: NOT YET DOCUMENTED. nope, still blank πŸ’€
  • arcs β€” TODO: NOT YET DOCUMENTED. and that's the last one. We love a consistent queen.
no fr, all four of those TODO notes are straight from the original page. I'm not gatekeeping anything, there's just genuinely nothing there to tell you πŸ™ˆ

🌈 DESCRIPTION 🌈

...okay so this section is empty in the original. Like, fully empty. Nothing. A void. A blank space where lore should be. Not me inventing things to fill it β€” that would be lying to you, and I would never πŸ’œ


⭐ RETURN VALUE ⭐

It hands you back an xcb_void_cookie_t. Slay. And the errors β€” if there are any β€” have to be handled over in the event loop, so don't come crying to the return value about it.

If you'd rather deal with errors directly, with xcb_request_check instead of the event loop route, then bestie you want xcb_poly_fill_arc_checked. The xcb-requests(3) page has the details, go check it πŸŽ€


πŸ’€ ERRORS πŸ’€

Good news for once: this request does never generate any errors. Zero. None. A clean queen. πŸ‘‘


🧚 SEE ALSO 🧚

...also empty in the original. Nothing listed here. So there's nothing for me to link you to and I'm not gonna make something up, that's not the move πŸ’–


πŸ‘‘ AUTHOR πŸ‘‘

Generated from xproto.xml. And if you spot something wrong or wanna suggest improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who take corrections, not me, I'm just the messenger 🫢


and that's the whole page, bestie!! thanks for reading, mwah πŸ’…βœ¨

this lil transmission came to you from X Version 11, libxcb 1.17.0, and it's the xcb_poly_fill_arc(3) page β€” catch you in the next one, love u, bye!! πŸŽ€πŸ¦‹πŸŒΈ