xcb_damage_subtract(3)
π xcb_damage_subtract π
okay bestie, welcome to the xcb_damage_subtract page from the XCB Requests manual π this one is short and sweet and honestly? a little mysterious. let's get into it β¨
πΈ NAME πΈ
xcb_damage_subtract β remove regions from a previously created Damage object.
like, you already made a Damage object, and now you're taking some regions back out of it. it's giving editing your damage receipts π§Ύβ¨
π SYNOPSIS π
first things first, you gotta pull in the header:
#include <xcb/damage.h>
β¨ Request function β¨
xcb_void_cookie_t xcb_damage_subtract(xcb_connection_t *conn,
xcb_damage_damage_t damage, xcb_xfixes_region_t repair,
xcb_xfixes_region_t parts);
that's the whole vibe. four things go in, a xcb_void_cookie_t comes out π«Ά
π¦ REQUEST ARGUMENTS π¦
connβ the XCB connection to X11. your lil phone line to the server, no cap πdamageβ the ID you provided toxcb_create_damage. yes, that damage. the one you made earlier, bestie πrepairβ TODO: NOT YET DOCUMENTED. yeahβ¦ nobody wrote this one down yet πpartsβ TODO: NOT YET DOCUMENTED. also a mystery. iconic of them honestly π
not me telling you two of the args are literally undocumented. that's just what the page says, i'm not gonna make stuff up π
π DESCRIPTION π
so what does this actually do? it updates the regions of damage recorded in a a Damage object. yes, the double "a a" is in the original, we keep it, we don't touch it, it's part of the lore now π
for the full tea, go read:
https://www.x.org/releases/current/doc/damageproto/damageproto.txt
that's where the details live, bestie πβ¨
β RETURN VALUE β
it returns an xcb_void_cookie_t. so if there are errors (if any π), you gotta handle them in the event loop. that's just how it is.
if you'd rather deal with errors directly using xcb_request_check instead, then use xcb_damage_subtract_checked. see xcb-requests(3) for the details, iykyk π«Ά
π ERRORS π
this request does never generate any errors.
periodt. zero. none. clean slate. no error drama here β¨
π SEE ALSO π
π AUTHOR π
Generated from damage.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
so if something's off, that's the inbox to slide into π¬
and that's the whole page, bestie!! you ate this one fr fr πΈπ¦ no errors, no drama, just vibes and an undocumented arg or two.
this has been X Version 11, libxcb 1.17.0, brought to you by the xcb_damage_subtract(3) girlies πβ¨π mwah, go subtract some regions π«Ά
π¦ 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