XOSD_DESTROY(3)

💖 XOSD_DESTROY(3) 💖

okay bestie, gather round, we're talking about xosd_destroy from the XOSD manual, section 3 🎀

---

✨ NAME ✨

xosd_destroy — say bye-bye to an XOSD object, like, permanently 💅

---

🌸 SYNOPSIS 🌸

#include <xosd.h>

int xosd_destroy (xosd *osd);

---

🦋 DESCRIPTION 🦋

so xosd_destroy does exactly what it says on the tin: it destroys an XOSD object and frees up any memory that object was using. no leaks, no leftovers, we love a clean exit 💖

but listen — the osd object you're yeeting here must have been created by xosd_create(3xosd) first. you can't just destroy a random pointer and expect it to go well, that's not the vibe 🫶

and ngl, xosd_destroy is not intended to be used on its own. it's a helper function, doing its little job from inside the display_info tool. it's giving supporting character, and honestly? we respect it ✨

---

🌈 ARGUMENTS 🌈

• osd — the object you're destroying. the one getting the goodbye kiss 💀

---

💜 RETURN VALUE 💜

• on success, 1 comes back to you 🎉
• otherwise you get 0, and xosd_error gets set so you actually know why things went sideways 😭

---

🧚 ENVIRONMENT 🧚

• char *xosd_error — a string pointing to a text string that describes the error, if one occurred. basically the little note explaining what went wrong 🍓

---

⭐ HISTORY ⭐

xosd_destroy first appeared in version 2.0 of the XOSD library, where it replaced the now-deprecated xosd_uninit function. out with the old, in with the iconic 👑

---

👑 AUTHORS 👑

the XOSD library was originally written by André Renaud, and is currently maintained by Tim Wright. this document was written by Michael JasonSmith 🫶

---

🙈 BUGS 🙈

there are no known bugs with xosd_destroy. periodt. but if you find one, bug reports can be sent to <xosd@ignavus.net> — they wanna hear it fr fr 💌

---

🔥 SEE ALSO 🔥

• xosd_create(3) — the origin story, the one who made the object you're about to destroy 🌸

---

and that's the whole page bestie!! this was XOSD_DESTROY(3) from the XOSD manual, section 3 — go forth, destroy responsibly, and remember: always xosd_create(3xosd) before you xosd_destroy 💖✨🎀