xcb_fill_poly(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_fill_poly ✨

ok bestie so this is a page from the XCB Requests section of the manual, it's xcb_fill_poly(3), and honestly? it's giving "polygon glow-up" πŸ’…


🌸 NAME 🌸

xcb_fill_poly β€” (and like… that's it, the description slot is literally empty, no cap πŸ’€)


πŸŽ€ SYNOPSIS πŸŽ€

First things first, you gotta bring in the header, periodt:

#include <xcb/xproto.h>

Request function

here's the whole vibe, copy it exactly bestie:

xcb_void_cookie_t xcb_fill_poly(xcb_connection_t *conn,
       xcb_drawable_t drawable, xcb_gcontext_t gc, uint8_t shape,
       uint8_t coordinate_mode, uint32_t points_len, const
       xcb_point_t *points);

πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11. your lil hotline to the server, iykyk 🫢
  • drawable β€” TODO: NOT YET DOCUMENTED. (the manpage really said "mystery ✨")
  • gc β€” TODO: NOT YET DOCUMENTED. (also a mystery, bestie, we don't make the rules 😭)
  • shape β€” it's one of these values, pick your fighter:
    • XCB_POLY_SHAPE_COMPLEX β€” TODO: NOT YET DOCUMENTED.
    • XCB_POLY_SHAPE_NONCONVEX β€” TODO: NOT YET DOCUMENTED.
    • XCB_POLY_SHAPE_CONVEX β€” TODO: NOT YET DOCUMENTED.
    • TODO: NOT YET DOCUMENTED. (yeah this extra TODO is just… vibing here on its own. iconic behaviour honestly 🌈)
  • coordinate_mode β€” also a pick-one situation:
    • XCB_COORD_MODE_ORIGIN β€” Treats all coordinates as relative to the origin.
    • XCB_COORD_MODE_PREVIOUS β€” Treats all coordinates after the first as relative to the previous coordinate.
    • TODO: NOT YET DOCUMENTED. (another solo TODO, main character energy πŸ’€)
  • points_len β€” TODO: NOT YET DOCUMENTED.
  • points β€” TODO: NOT YET DOCUMENTED.

πŸ’– DESCRIPTION πŸ’–

bestie… there is literally nothing here. the DESCRIPTION section is empty. it's giving silence. it's giving "we'll fill it in later". no tea, no shade, just an empty section. 🫠

🌟 RETURN VALUE 🌟

It hands you back an xcb_void_cookie_t. If any errors pop off, you have to deal with them in the event loop, not right here, okay?

If you'd rather handle errors directly with xcb_request_check instead, then use xcb_fill_poly_checked instead. Peep xcb-requests(3) for the deets. πŸ“š


πŸ”₯ ERRORS πŸ”₯

This request does never generate any errors. periodt. zero drama, we love a low-maintenance request ✨


🌈 SEE ALSO 🌈

bestie this section is empty too 😭 nothing to see, nothing to also. it's a whole vibe of absence.

πŸ‘‘ AUTHOR πŸ‘‘

Generated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes they really want your emails, bestie, slide into their inbox if something's off πŸ’Œ)


and that's the whole page! this was xcb_fill_poly(3) from X Version 11, libxcb 1.17.0, and the date line is blank so we're just gonna say sometime, whenever, no timestamp bestie πŸŽ€ stay slaying with your polygons, mwah πŸ’–βœ¨