xcb_render_tri_strip(3)
π xcb_render_tri_strip β the XCB Requests girlies
okay so bestie, welcome to xcb_render_tri_strip(3) from the XCB Requests collection π this is the libxcb corner of the X11 universe and we're about to read a whole manual page together, no skimming, no scrolling past the boring bits, periodt β¨
πΈ NAME πΈ
xcb_render_tri_strip β
and then... nothing. literally nothing. the description slot is empty, bestie π the manpage said "name:" and then went silent like a read receipt. iconic behaviour, honestly.
π¦ SYNOPSIS π¦
first things first, you gotta include the header:
#include <xcb/render.h>
β¨ Request function β¨
xcb_void_cookie_t xcb_render_tri_strip(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 points_len, const
xcb_render_pointfix_t *points);
look at her. nine parameters. she's high maintenance and we love that for her π
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil hotline to the server, your group chat with the display π«ΆopβTODO: NOT YET DOCUMENTED.yeah. the docs said "we'll get to it" and never did πsrcβTODO: NOT YET DOCUMENTED.same vibe, same void πdstβTODO: NOT YET DOCUMENTED.the documentation is not documenting today, bestiemask_formatβTODO: NOT YET DOCUMENTED.ngl the whole argument list is giving "unfinished homework" πsrc_xβTODO: NOT YET DOCUMENTED.fr frsrc_yβTODO: NOT YET DOCUMENTED.not a single crumb of lorepoints_lenβTODO: NOT YET DOCUMENTED.we know it's a length of something. that's the tea πpointsβTODO: NOT YET DOCUMENTED.and it's aconst xcb_render_pointfix_t *, so like, a pointer to pointfixes. that's all we're getting π§
no cap, every single one of these says TODO: NOT YET DOCUMENTED. in the original. i'm not hiding anything from you, that's genuinely the whole vibe check.
π DESCRIPTION π
there is a DESCRIPTION heading in the original. under it? nothing. empty. a whole heading with no body, like a fit pic with no fit π
π RETURN VALUE π
she returns an xcb_void_cookie_t, bestie π and here's the important part: any errors (if there even are any) have to be handled over in the event loop. so you don't just get handed your problems back, you gotta go find them.
if you'd rather deal with errors directly using xcb_request_check instead, then use xcb_render_tri_strip_checked. that's the checked girlie, she'll hand you the receipts π§Ύ
for the full deets, go read xcb-requests(3). iykyk.
β ERRORS β
this request does never generate any errors. not one. zero. she's unproblematic, she's drama-free, she simply does not start anything π β¨
π SEE ALSO π
...it's empty, bestie. there is nothing here. the SEE ALSO section has no see-alsos. we love a minimalist queen π
π AUTHOR π
Generated from render.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β so if you spot something off, you know exactly where to slide into the inbox π¬
and that's the whole page, bestie π«Ά this was xcb_render_tri_strip(3) from X Version 11, libxcb 1.17.0 β slay, bye, go render something iconic ππΈβ¨
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms