xcb_input_allow_device_events(3)

🌸 xcb_input_allow_device_events — the XCB Requests girlies' entry 💅

okay so bestie, this is the manual page for xcb_input_allow_device_events(3), living in the XCB Requests section of the manual. she's giving mysterious, she's giving cryptic, she's lowkey hiding her whole personality from us 😭 but we're gonna read her anyway, periodt.

---

✨ NAME ✨

so the NAME line is... literally empty. like, blank blank. nothing. the void. 🫥

no cap, the original page just has the function name and then a big fat nothing where the description should be. it's giving "she's an enigma". we move. 💀

---

🦋 SYNOPSIS 🦋

first up, you gotta pull in the header, bestie:

#include <xcb/xinput.h>

and here's the request function itself — copy it exactly, don't freestyle:

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

look at her. four args. no notes. 🎀

---

🌈 REQUEST ARGUMENTS 🌈

• conn — the XCB connection to X11. this is your link to the server, your main character hotline ☎️ every XCB request needs one, iykyk.
• time — TODO: NOT YET DOCUMENTED. yeah. that's it. that's the whole description. the docs said "we'll finish this later" and then simply did not 🙈
• mode — TODO: NOT YET DOCUMENTED. same energy, different parameter. iconic in a cursed way.
• device_id — TODO: NOT YET DOCUMENTED. bestie they really left all three of these on read 😭

---

💜 DESCRIPTION 💜

and the DESCRIPTION section is... empty too. like, nothing. zero. the silence is deafening. 🦗

this is one of those pages where the docs are still loading, so pls don't come for me — I'm just the messenger. all the vibes, none of the prose. ✨

---

💖 RETURN VALUE 💖

okay so here's actual info, slay:

this one returns an xcb_void_cookie_t. and because it's a void cookie, any errors (if there even are any) have to be handled over in your event loop, not right here. so set up your event loop, bestie, she's where the drama happens 🔥

and if you'd rather catch errors directly instead of waiting around in the event loop — and honestly, sometimes a girl just needs instant answers — use xcb_request_check instead, paired with xcb_input_allow_device_events_checked. 👑

for the full tea on how cookies and checked-vs-unchecked work, go read xcb-requests(3). it's the lore. 📚

---

🎀 ERRORS 🎀

good news, genuinely:

this request does never generate any errors. not one. zero errors. clean hands, clear conscience, no notes. 💅✨

so you can breathe, babe. this one's not gonna blow up in your face.

---

🌸 SEE ALSO 🌸

...nothing here either. the SEE ALSO section is empty. no cross-refs, no friends, just her standing alone in the hallway. solitude queen. 🦋

---

👑 AUTHOR 👑

this page was generated from xinput.xml. if you spot something wrong or wanna send corrections and improvements, hit up xcb@lists.freedesktop.org — they're literally asking for it, so don't be shy, bestie. 📧💖

---

and that's the whole page, fr fr. tysm for reading, ily 🫶

X Version 11 · libxcb 1.17.0 — that's the source and version, and this page is xcb_input_allow_device_events(3), so if you ever need her again, she's right there in the manual. mwah. 💋🌸✨