xcb_render_triangles(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_triangles β€” the XCB Requests girlies know πŸ’…

okay so bestie, we're in xcb_render_triangles(3) territory and it's giving "draw me some triangles, but make it a whole X request" πŸ¦‹ no cap.


🌸 NAME 🌸

xcb_render_triangles β€” literally that's the whole name, the description slot is just sitting there empty like a group chat where nobody's typed yet 😭


✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/render.h>

πŸŽ€ Request function πŸŽ€

here's the whole signature, character for character, don't @ me:

xcb_void_cookie_t xcb_render_triangles(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 triangles_len, const
       xcb_render_triangle_t *triangles);

πŸ’– REQUEST ARGUMENTS πŸ’–

okay so let's go through the whole cast, one by one, main character energy only:

  • conn β€” the XCB connection to X11. your little phone line to the server, basically πŸ“ž
  • op β€” TODO: NOT YET DOCUMENTED. (the docs really said "we'll get to it" and never did πŸ™ˆ)
  • 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.
  • triangles_len β€” TODO: NOT YET DOCUMENTED.
  • triangles β€” TODO: NOT YET DOCUMENTED.
not me listing all of these and every single one is a TODO πŸ’€ the mystery is the vibe, I guess. the parameter names and types are all we got and we're keeping them exactly as-is, periodt.

🌈 DESCRIPTION 🌈

bestie... there is literally nothing here. the DESCRIPTION section is empty. a blank canvas. a silent group chat. the manpage equivalent of sending "..." and leaving it at that 🫢


⭐ RETURN VALUE ⭐

so it hands you back an xcb_void_cookie_t. it's a void cookie, which means any errors have to be caught over in the event loop, not handed to you directly πŸ“

if you'd rather deal with errors right away using xcb_request_check, then use xcb_render_triangles_checked instead. full details live in xcb-requests(3) if you wanna go deeper πŸ‘‘


πŸ”₯ ERRORS πŸ”₯

this request does never generate any errors. like, zero. none. she's unbothered, moisturized, in her lane πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

...and that's it. the SEE ALSO section is empty too. iconic of her honestly 🌸


πŸ’œ AUTHOR πŸ’œ

generated from render.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're the ones to tell, fr fr πŸ“§


okay that's the whole page, bestie, we ate and left no crumbs πŸŽ€ this was X Version 11, libxcb 1.17.0, and yeah β€” the header said XCB Requests, the footer said xcb_render_triangles(3), so now you know the whole lore. bye bestie, go draw some triangles πŸ’–βœ¨πŸ¦‹