xcb_input_grab_device(3)

💖 xcb_input_grab_device — the XCB Requests girlies' guide 💖

okay so bestie, we're in the xcb_input_grab_device(3) zone today, part of the XCB Requests family, and honestly? it's giving "grab that device" and we're obsessed. no cap.

---

✨ NAME ✨

xcb_input_grab_device — bestie the docs literally left this one blank, it's just vibes and a dash. we move. 💅

---

🌸 SYNOPSIS 🌸

first up, the include, as always:

#include <xcb/xinput.h>

🎀 Request function 🎀

xcb_input_grab_device_cookie_t
       xcb_input_grab_device(xcb_connection_t *conn,
       xcb_window_t grab_window, xcb_timestamp_t time,
       uint16_t num_classes, uint8_t this_device_mode,
       uint8_t other_device_mode, uint8_t owner_events,
       uint8_t device_id, const xcb_input_event_class_t *classes);

🦋 Reply datastructure 🦋

typedef struct xcb_input_grab_device_reply_t {
    uint8_t  response_type;
    uint8_t  xi_reply_type;
    uint16_t sequence;
    uint32_t length;
    uint8_t  status;
    uint8_t  pad0[23];
} xcb_input_grab_device_reply_t;

⭐ Reply function ⭐

xcb_input_grab_device_reply_t
       *xcb_input_grab_device_reply(xcb_connection_t *conn,
       xcb_input_grab_device_cookie_t cookie, xcb_generic_error_t **e);

---

💜 REQUEST ARGUMENTS 💜

• conn — your XCB connection to X11. the whole link-up, the main character of the connection-verse fr fr.
• grab_window — TODO: NOT YET DOCUMENTED. yeah. the manpage said nothing. we're all just sitting here. 😭
• time — TODO: NOT YET DOCUMENTED. still nothing bestie, not a single crumb.
• num_classes — TODO: NOT YET DOCUMENTED. the silence is loud.
• this_device_mode — TODO: NOT YET DOCUMENTED. undoc'd and unbothered.
• other_device_mode — TODO: NOT YET DOCUMENTED. also no thoughts, just a placeholder.
• owner_events — TODO: NOT YET DOCUMENTED. we know nothing, and honestly that's iconic of the maintainers.
• device_id — TODO: NOT YET DOCUMENTED. yeah, the one you'd most wanna know about. nope. 🙈
• classes — TODO: NOT YET DOCUMENTED. same energy, same emptiness.

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, and in this case it's XCB_INPUT_GRAB_DEVICE. lowkey the most useful thing here: this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other. vibe check your replies, basically. ✨
• sequence — the sequence number of the last request that got processed by the X11 server. the receipts, if you will.
• length — the length of the reply, counted in words. and btw a word here is 4 bytes, in case anyone was about to do math wrong. 🧚
• xi_reply_type — TODO: NOT YET DOCUMENTED. no crumbs. 💀
• status — TODO: NOT YET DOCUMENTED. also blank, also tragic.

---

🫶 DESCRIPTION 🫶

...and that's it. that's the section. literally empty. the DESCRIPTION section has left the chat. 😭

---

👑 RETURN VALUE 👑

Returns an xcb_input_grab_device_cookie_t. slay. but listen — errors? you have to handle those yourself when you call the reply function xcb_input_grab_device_reply.

If you'd rather handle errors in the event loop instead (valid, honestly), use xcb_input_grab_device_unchecked. and for the full tea on how requests work, go read xcb-requests(3). iykyk.

---

💀 ERRORS 💀

This request does never generate any errors. periodt. zero errors, zero drama.

---

🔥 SEE ALSO 🔥

...nothing. the SEE ALSO section is a ghost town. bestie. 💀

---

💅 AUTHOR 💅

Generated from xinput.xml. if you've got corrections and improvements, contact xcb@lists.freedesktop.org — they want your notes, fr fr.

---

and that's the whole page bestie!! this one shipped with X Version 11, libxcb 1.17.0, and that sweet xcb_input_grab_device(3) energy. mwah. go grab that device. 🎀✨🦋💖