xcb_input_xi_...ungrab_device(3)

💜 xcb_input_xi_passive_ungrab_device(3) 💜

okay bestie, so this is a page from the XCB Requests manual — that's the X protocol C binding situation — and it's literally called xcb_input_xi_...ungrab_device. yes the name is abbreviated like that, it's giving mysterious main character energy and we're not gonna argue with it. 🌸

---

✨ NAME ✨

xcb_input_xi_passive_ungrab_device — the passive ungrab device request, bestie. that's it, that's the whole name, the description line is literally just vibes and a dash. 💅

---

✨ SYNOPSIS ✨

first up, you gotta pull in the header, no cap:

#include <xcb/xinput.h>

🎀 Request function

and here's the actual function, character for character, don't @ me:

xcb_void_cookie_t
       xcb_input_xi_passive_ungrab_device(xcb_connection_t *conn,
       xcb_window_t grab_window, uint32_t detail,
       xcb_input_device_id_t deviceid, uint16_t num_modifiers,
       uint8_t grab_type, const uint32_t *modifiers);

she's long, she's loaded, she's iconic. 👑

---

✨ REQUEST ARGUMENTS ✨

here's every single thing you're feeding her, and what the docs say about each one:

• conn — the XCB connection to X11, obvi. it's your link to the whole X situation, the group chat with the server if you will. 🫶
• grab_window — TODO: NOT YET DOCUMENTED. yeah girl, they left it blank, we report the blank faithfully. 😭
• detail — TODO: NOT YET DOCUMENTED. same energy, same blank. 🙈
• deviceid — TODO: NOT YET DOCUMENTED. mystery device, mystery docs. 💀
• num_modifiers — TODO: NOT YET DOCUMENTED. how many modifiers? the docs refuse to say. ✨
• grab_type — TODO: NOT YET DOCUMENTED. type of grab, allegedly, per the name, but the page is silent. 🌙
• modifiers — TODO: NOT YET DOCUMENTED. the pointer to the modifiers, also undocumented. ⭐

ngl bestie, that's a LOT of TODO: NOT YET DOCUMENTED. in one place. it's not me being lazy, that's literally what the page says. i would never leave you hanging like that. 💖

---

✨ DESCRIPTION ✨

okay so… the DESCRIPTION section? it's empty. completely, absolutely empty. not a single word. it's giving "we'll finish this later" and later never came. 😭

what i can tell you is that this is the xcb_input_xi_passive_ungrab_device request function from <xcb/xinput.h>, generated from xinput.xml — and that's all the page itself gives us. no invented lore, no guessing, periodt. 💅

---

✨ RETURN VALUE ✨

she returns an xcb_void_cookie_t, bestie. 🔥 and listen — errors (if any) have to be handled in the event loop. that's the deal.

but if you'd rather handle errors directly, you use xcb_request_check instead, and for that you want:

xcb_input_xi_passive_ungrab_device_checked

and if you want the whole tea on how request checking works, go read xcb-requests(3). it's all in there. 🫶

---

✨ ERRORS ✨

good news, babe: this request does never generate any errors. 🌈 zero. none. clean slate, no drama, no error codes to catch. slay.

---

✨ SEE ALSO ✨

this section is… empty. nothing listed. that's just how the page is, we don't make stuff up around here. 🦋

---

✨ AUTHOR ✨

this whole thing was generated from xinput.xml. if you spot something wrong and wanna help fix it, hit up xcb@lists.freedesktop.org — they take corrections and improvements, fr fr. 💌

---

and that's the page, bestie!! 🎀 go forth and ungrab those passive devices (once somebody documents what all those arguments actually do, lmaooo). mwah. 💅✨

X Version 11 · libxcb 1.17.0 · xcb_input_xi_...ungrab_device(3) — that's the footer tea, sourcing and version and everything, signing off like the icon she is. 👑💖