xcb_poly_fill_rectangle(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_rectangle ✨

okay bestie, welcome to xcb_poly_fill_rectangle — the XCB Requests page that literally just fills rectangles for you 💖 like yes, that's the whole job, and she does it beautifully.

🌸 NAME 🌸

xcb_poly_fill_rectangle — fills rectangles 🎀

🦋 SYNOPSIS 🦋

#include <xcb/xproto.h>

💅 Request function

xcb_void_cookie_t xcb_poly_fill_rectangle(xcb_connection_t *conn,
       xcb_drawable_t drawable, xcb_gcontext_t gc,
       uint32_t rectangles_len, const xcb_rectangle_t *rectangles);

👑 REQUEST ARGUMENTS 👑

  • conn — your XCB connection to X11. the whole group chat line to the server, basically 🫶
  • drawable — the drawable (Window or Pixmap) you're drawing on. pick your canvas, bestie 🎨
  • gc — the graphics context to use. and listen, she's not a one-trick pony, so here's exactly what she pulls from:

the following graphics context components are used: function, plane-mask, fill-style, subwindow-mode, clip-x-origin, clip-y-origin, and clip-mask. ⭐

the following graphics context mode-dependent components are used: foreground, background, tile, stipple, tile-stipple-x-origin, and tile-stipple-y-origin. 💅

  • rectangles_len — the number of xcb_rectangle_t structures in rectangles. like, how many are we doing? 🔢
  • rectangles — the rectangles to fill. the actual squad of shapes, periodt 🍓

💖 DESCRIPTION 💖

She fills the specified rectangle(s) in the order listed in the array. no cap, order matters, that's just the vibe.

for any given rectangle, each pixel is not drawn more than once. so no self-overlap drama within one rectangle, we love a clean queen ✨

but — and this is the tea — if rectangles intersect, the intersecting pixels are drawn multiple times. so like, if your shapes overlap, that overlap is getting painted again and again. not me warning you about your own geometry 😭

🌈 RETURN VALUE 🌈

returns an xcb_void_cookie_t. and here's the thing: errors (if any) have to be handled in the event loop, okay? that's just how she rolls 🎀

if you want to handle errors directly with xcb_request_check instead, use xcb_poly_fill_rectangle_checked. see xcb-requests(3) for details 💜

💀 ERRORS 💀

  • xcb_drawable_error_t — the specified drawable (Window or Pixmap) does not exist. gone. not found. she's not there bestie 🙈
  • xcb_g_context_error_t — the specified graphics context does not exist. also missing, also a problem 😭
  • xcb_match_error_t — TODO: reasons? ... yeah the manpage itself is like "idk lol". iconic honestly 💅

🫶 SEE ALSO 🫶

🌟 AUTHOR 🌟

generated from xproto.xml. contact xcb@lists.freedesktop.org for corrections and improvements 📧 like if something's off, tell the mailing list, they're the ones who can fix it fr fr.

and that's the whole page bestie, you ate that 🎀 this was xcb_poly_fill_rectangle(3) from the XCB Requests crew, part of X Version 11, libxcb 1.17.0 — go fill some rectangles, ily, bye 💖✨🦋

📦 where this page comes from