xcb_input_ungrab_device(3)

xcb_input_ungrab_device 💅

okay bestie, welcome to the xcb_input_ungrab_device(3) page — it's an XCB Requests girlie, and she's here to let your grabbed device go. no cap. 🦋

---

✨ NAME ✨

xcb_input_ungrab_device — literally just the name, that's it, the original left it blank bestie (the manpage's NAME line is empty, so we're not inventing anything 🙈)

---

🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header:

#include <xcb/xinput.h>

Request function 🎀

xcb_void_cookie_t xcb_input_ungrab_device(xcb_connection_t *conn,
       xcb_timestamp_t time, uint8_t device_id);

---

💖 REQUEST ARGUMENTS 💖

• conn — your XCB connection to X11, the whole vibe pipeline to the server. 🔥
• time — TODO: NOT YET DOCUMENTED. not me knowing nothing about this one 😭
• device_id — TODO: NOT YET DOCUMENTED. same energy, fr fr 🫶

---

🦋 DESCRIPTION 🦋

So… the DESCRIPTION section? it's empty. Genuinely nothing there. The original page said nothing and I'm not about to make stuff up, so we're all just gonna sit in this silence together 💀

---

⭐ RETURN VALUE ⭐

She hands you back an xcb_void_cookie_t, bestie. Errors (if any) have to be handled in the event loop. That's the whole deal.

But wait — if you'd rather handle errors directly with xcb_request_check instead, use xcb_input_ungrab_device_checked. She's the checked version, she's iconic, she's got you. 👑

See xcb-requests(3) for the details, iykyk. ✨

---

🎀 ERRORS 🎀

This request does never generate any errors.

not a single error, not even one. flawless behavior honestly. 💅✨

---

🌈 SEE ALSO 🌈

…nothing. absolutely nothing listed. the section is there and it is empty. ghost town. 🍓

---

💜 AUTHOR 💜

Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. 🫶

---

and that's the whole page, bestie — X Version 11, libxcb 1.17.0, and yes the footer really does call her xcb_input_ungrab_device(3). slay, go ungrab that device, ily 💖🌸🧚