xcb_input_query_device_state(3)

✨ xcb_input_query_device_state ✨

okay bestie, welcome to the XCB Requests chapter of the manual, section 3 💅 this one is xcb_input_query_device_state and she is lowkey iconic — she asks the X server "hey queen, what's the current state of this device?" and the server tells you. that's the whole vibe. no cap.

---

🌸 NAME 🌸

xcb_input_query_device_state — (the original page leaves this blank, so like… that's all we got, bestie 🙈)

---

🎀 SYNOPSIS 🎀

first up, you gotta pull in the header:

#include <xcb/xinput.h>

Request function

xcb_input_query_device_state_cookie_t
       xcb_input_query_device_state(xcb_connection_t *conn,
       uint8_t device_id);

Reply datastructure

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

Reply function

xcb_input_query_device_state_reply_t
       *xcb_input_query_device_state_reply(xcb_connection_t *conn,
       xcb_input_query_device_state_cookie_t cookie,
       xcb_generic_error_t **e);

Reply accessors

int xcb_input_query_device_state_classes_length(const
       xcb_input_query_device_state_reply_t *reply);

xcb_input_input_state_iterator_t
       xcb_input_query_device_state_classes_iterator(const
       xcb_input_query_device_state_reply_t *reply);

---

👑 REQUEST ARGUMENTS 👑

• conn — the XCB connection to X11. your little hotline to the server, fr fr.
• device_id — TODO: NOT YET DOCUMENTED. yeah bestie, the upstream docs left this one on read 😭 it's a uint8_t and it's the device you're asking about, that's all we know.

---

🦋 REPLY FIELDS 🦋

• response_type — the type of this reply. in this case it's XCB_INPUT_QUERY_DEVICE_STATE. this field is also present in the xcb_generic_reply_t, and it's literally how you tell replies apart from each other 💅
• sequence — the sequence number of the last request processed by the X11 server. her little receipt number 🧾
• length — the length of the reply, in words. and a word is 4 bytes, so do the math bestie.
• xi_reply_type — TODO: NOT YET DOCUMENTED. 🙈
• num_classes — TODO: NOT YET DOCUMENTED. 🙈

---

🌈 DESCRIPTION 🌈

nothing here, bestie. the original page has an empty DESCRIPTION section. the silence is deafening 💀

---

⭐ RETURN VALUE ⭐

she returns an xcb_input_query_device_state_cookie_t 🍪 — that's your little claim ticket.

errors have to be handled when you call the reply function xcb_input_query_device_state_reply, okay? that's the moment of truth.

and if you'd rather handle errors in the event loop instead? use xcb_input_query_device_state_unchecked. see xcb-requests(3) for the deets, iykyk.

---

💜 ERRORS 💜

this request does never generate any errors. periodt. not a single one. flawless behavior honestly 🔥

---

🌟 SEE ALSO 🌟

this section is empty on the original page too 🫶 nothing to link, nothing to see, moving on.

---

🍓 AUTHOR 🍓

generated from xinput.xml. if you spot something wrong or wanna make it better, hit up xcb@lists.freedesktop.org for corrections and improvements — they're literally waiting for your email bestie 💌

---

and that's the whole page!! this beauty came to you from X Version 11, libxcb 1.17.0, and she is xcb_input_query_device_state(3) — slay, stay hydrated, and remember: cookies don't eat themselves 🍪✨💖