xcb_render_fill_rectangles(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_fill_rectangles πŸ’…

okay bestie, so this one is a page from the XCB Requests corner of the libxcb universe ✨ (XCB = X protocol C-language Binding, and she's serving real ones, fr fr).


🌸 NAME 🌸

xcb_render_fill_rectangles β€” and then… nothing?? 😭 The description field on this one is literally empty. Not me getting a whole NAME section with the dash and no words after it. It's giving mystery. It's giving "the docs said πŸ’€". We move anyway πŸ’–


πŸŽ€ SYNOPSIS πŸŽ€

✨ Request function ✨

#include <xcb/render.h>

xcb_void_cookie_t xcb_render_fill_rectangles(xcb_connection_t *conn,
       uint8_t op, xcb_render_picture_t dst, xcb_render_color_t color,
       uint32_t rects_len, const xcb_rectangle_t *rects);

so first you gotta pull in <xcb/render.h> β€” that's the header, she's essential, no skips 🫢 β€” and then you call that function with those six things. Look at her. Iconic signature. ⭐


πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” bestie this is your XCB connection to X11. Your lil hotline to the server. πŸ’œ
  • op β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ
  • dst β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ
  • color β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ
  • rects_len β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ
  • rects β€” TODO: NOT YET DOCUMENTED. πŸ™ˆ
ngl, five out of six of these are straight up "TODO: NOT YET DOCUMENTED." and I'm not about to make up lore for them, because inventing behaviour is not the vibe. The docs are the docs, and right now they're saying nothing. Periodt. 😭 We respect the mystery. πŸ’…

πŸ’– DESCRIPTION πŸ’–

also empty. Like, genuinely nothing here. The original page has a DESCRIPTION heading and then just… air. 🌬️ So consider this your moment of silence, bestie. πŸŽ€


πŸ”₯ RETURN VALUE πŸ”₯

She returns an xcb_void_cookie_t. πŸ’« And here's the tea: errors (if there are any) have to be handled in the event loop. That's the deal.

If you'd rather handle errors directly with xcb_request_check, then use xcb_render_fill_rectangles_checked instead β€” that's her checked twin, she'll tell you what went wrong. πŸ’…

For the full story on how any of this cookie business works, go see xcb-requests(3). πŸ‘‘


😭 ERRORS 😭

This request does never generate any errors.

yup. zero. none. she's perfect, she's unbothered, she cannot fail you like that. 🌈 (Obviously still handle your cookie in the event loop like a responsible main character, but there's nothing to catch. Slay.)


πŸ‘‘ SEE ALSO πŸ‘‘

…bestie there's literally nothing listed here. The section exists, the entries do not. It's giving an empty group chat. 🫢


✨ AUTHOR ✨

Generated from render.xml. πŸ“œ Contact xcb@lists.freedesktop.org for corrections and improvements. (If you know what op, dst, color, rects_len and rects actually do β€” please email them, they're begging. πŸ™)


okay that's the whole page, we ate and left no crumbs πŸ’… this was X Version 11, libxcb 1.17.0, and it's xcb_render_fill_rectangles(3) β€” ily, go fill some rectangles bestie πŸŽ€βœ¨πŸ’–