xcb_damage_destroy(3)

📦
version 1.17.0 · 5 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_damage_destroy 💅

okay bestie, welcome to the XCB Requests corner of the manual, page xcb_damage_destroy(3), from the one and only libxcb ✨

NAME 🎀

xcb_damage_destroy — literally destroys a Damage object you made earlier. bye bye 👋

SYNOPSIS 🌸

#include <xcb/damage.h>

Request function 🦋

xcb_void_cookie_t xcb_damage_destroy(xcb_connection_t *conn,
       xcb_damage_damage_t damage);

REQUEST ARGUMENTS 💖

  • conn — the XCB connection to X11. your lil link to the server, your main character ✨
  • damage — the ID you provided to xcb_create_damage. yes, that ID. the one you made. you know the one 💅

DESCRIPTION 🌈

so what this does is: it destroys a Damage object, and it requests the X server stop reporting the changes it was tracking. that's it. that's the whole vibe. the damage era is over, the server stops gossiping about those changes to you 🫶

RETURN VALUE ⭐

Returns an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop. no cap, you gotta catch them yourself 😭

If you want to handle errors directly with xcb_request_check instead, use xcb_damage_destroy_checked. See xcb-requests(3) for details. iykyk 💜

ERRORS 🙈

This request does never generate any errors. not one. zero. she's flawless, she's unbothered, she ate 👑

SEE ALSO 🧚

AUTHOR 💀

Generated from damage.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes bestie, email the list, they're nice fr fr 💖)

okay that's the whole page, slay 🎀 and just so you know where this lil masterpiece came from: it's from X Version 11, rocking libxcb 1.17.0 🔥 no date on this one, she's timeless like that 💅 periodt.

📦 where this page comes from