xcb_damage_add(3)
π xcb_damage_add β the XCB Requests girlies' guide π
okay so bestie, welcome to xcb_damage_add(3) from the XCB Requests collection. this is the lil request that says "hey, add a region to a Damage object you already made earlier" β¨ no cap.
β¨ NAME β¨
xcb_damage_add β add a region to a previously created Damage object. that's it, that's the whole vibe π
πΈ SYNOPSIS πΈ
first things first, you gotta let the compiler know what's up:
#include <xcb/damage.h>
π¦ Request function π¦
here's the iconic signature, copy it exactly bestie, character for character:
xcb_void_cookie_t xcb_damage_add(xcb_connection_t *conn,
xcb_drawable_t drawable, xcb_xfixes_region_t region);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil hotline to the X server, she's the main character here fr.drawableβ TODO: NOT YET DOCUMENTED. yeah bestie the docs literally say that, i'm not gatekeeping, that's just what it says πregionβ TODO: NOT YET DOCUMENTED. same energy, the source material left this one blank, so blank it stays π
π DESCRIPTION π
so what does this actually do? it updates the regions of damage recorded in a a Damage object. (yes, "a a" β that's what the original says, i am not touching it, it's giving typo but it's their typo and it's iconic π)
want the full lore? the damage protocol tea lives right here:
https://www.x.org/releases/current/doc/damageproto/damageproto.txt
go read it, iykyk πβ¨
π₯ RETURN VALUE π₯
it hands you back an xcb_void_cookie_t. and because this is a void cookie, any errors that pop off have to be handled in the event loop β you don't get them handed to you directly, bestie, you gotta go get them.
if you do want to handle errors directly with xcb_request_check instead? then you want the checked version, xcb_damage_add_checked. see xcb-requests(3) for the deets π«Ά
π ERRORS π
good news queen: this request does never generate any errors. zero. none. a clean slate, a flawless vibe check, she simply does not miss π β¨
π SEE ALSO π
xcb-requests(3)β go read it, it's the blueprint fr fr
π AUTHOR π
Generated from damage.xml. need corrections or improvements? hit up xcb@lists.freedesktop.org β they're the ones holding the pen ποΈπ
and that's the whole page bestie!! this lil masterpiece came to you from X Version 11, libxcb 1.17.0, and the manpage xcb_damage_add(3) herself. slay, study, and go add those regions π¦π periodt β¨
π¦ 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