xcb_xfixes_se...e_clip_region(3)
π NAME π
xcb_xfixes_set_picture_clip_region β okay bestie, this one's a lil mystery box, the description line is literally just a dash, no cap π«Ά
It lives in the XCB Requests corner of the manual (that's the manual name, if you were wondering β xcb_xfixes_se...e_clip_region(3), which is giving truncated-title energy fr fr).
β¨ SYNOPSIS β¨
First things first, you gotta pull in the header:
#include <xcb/xfixes.h>
π Request function
xcb_void_cookie_t
xcb_xfixes_set_picture_clip_region(xcb_connection_t *conn,
xcb_render_picture_t picture, xcb_xfixes_region_t region,
int16_t x_origin, int16_t y_origin);
That's the whole signature, copy it exactly, don't freestyle it π
πΈ REQUEST ARGUMENTS πΈ
connβ the XCB connection to X11. Your lil lifeline to the server, the main character of every XCB call tbh.pictureβTODO: NOT YET DOCUMENTED.Yeah. The docs simply did not show up to the function. Not me exposing the upstream docs like this πregionβTODO: NOT YET DOCUMENTED.Same vibe, same silence πx_originβTODO: NOT YET DOCUMENTED.It's anint16_t, that's what we know, that's what we're working with πy_originβTODO: NOT YET DOCUMENTED.Alsoint16_t, also mysterious, also iconic in its elusiveness β¨
Lowkey important: I am not gonna invent meanings for these four, because the manual genuinely doesn't document them. If you need the deets, go read the source, bestie, I'm not gonna lie to you π«Ά
π¦ DESCRIPTION π¦
Soβ¦ there's a DESCRIPTION heading, and then there is nothing under it. Empty. Void. The girls said nothing. It's giving "we ran out of time before the release" energy π
β RETURN VALUE β
Returns an xcb_void_cookie_t. And because it's a void cookie, any errors (if there even are any) have to be handled over in the event loop β that's just how the void-cookie girlies operate.
If you'd rather handle errors directly with xcb_request_check instead, then use xcb_xfixes_set_picture_clip_region_checked. She's the checked twin π For all the details, go read xcb-requests(3).
π ERRORS π
This request does never generate any errors. Zero. None. Clean slate, no drama, we love a low-maintenance call π
π₯ SEE ALSO π₯
Okay so this section is hereβ¦ and it's empty. No references. Nothing to see. Literally nothing to also-see. Not me staring at a blank section π
π AUTHOR π
Generated from xfixes.xml. If you spot something wrong or wanna send improvements, hit up xcb@lists.freedesktop.org β they're the ones who take the corrections and improvements, periodt.
And that's the whole page, bestie!! π Written up as part of X Version 11, libxcb 1.17.0 β thanks for reading all the way through, you absolute icon, mwah πβ¨
π¦ 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