xcb_input_lis...ce_properties(3)

✨ xcb_input_list_device_properties ✨

okay bestie, so this is a page from the XCB Requests manual (yes, the X protocol binding girlies), and it's all about xcb_input_list_device_properties — a lil request that asks the X server for the properties hanging off one of your input devices. it's giving "let me see what's on that device's resume" energy. 💅

---

🌸 NAME 🌸

xcb_input_list_device_properties — ngl the original page literally just leaves this blank after the dash, so like… the name is the name, bestie. we move. 💖

---

✨ SYNOPSIS ✨

first up, you gotta pull in the header:

#include <xcb/xinput.h>

🎀 Request function

xcb_input_list_device_properties_cookie_t
       xcb_input_list_device_properties(xcb_connection_t *conn,
       uint8_t device_id);

🦋 Reply datastructure

this is the struct that comes back, and every field matters, so here it is in all its glory, no cap:

typedef struct xcb_input_list_device_properties_reply_t {
    uint8_t  response_type;
    uint8_t  xi_reply_type;
    uint16_t sequence;
    uint32_t length;
    uint16_t num_atoms;
    uint8_t  pad0[22];
} xcb_input_list_device_properties_reply_t;

💜 Reply function

xcb_input_list_device_properties_reply_t
       *xcb_input_list_device_properties_reply(xcb_connection_t *conn,
       xcb_input_list_device_properties_cookie_t cookie,
       xcb_generic_error_t **e);

🌈 Reply accessors

these are the little helpers that dig into the reply for you — lowkey obsessed with them:

xcb_atom_t *xcb_input_list_device_properties_atoms(const
       xcb_input_list_device_properties_request_t *reply);

int xcb_input_list_device_properties_atoms_length(const
       xcb_input_list_device_properties_reply_t *reply);

xcb_generic_iterator_t xcb_input_list_device_properties_atoms_end(const
       xcb_input_list_device_properties_reply_t *reply);

---

🫶 REQUEST ARGUMENTS 🫶

• conn — the XCB connection to X11. your lil hotline to the server, basically. 📞
• device_id — TODO: NOT YET DOCUMENTED. yeah bestie, even the manpage authors were like "we'll get to it". 🙈

---

💖 REPLY FIELDS 💖

• response_type — the type of this reply, and in this case it's XCB_INPUT_LIST_DEVICE_PROPERTIES. this field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. so like, it's the reply's whole identity. main character energy. 👑
• sequence — the sequence number of the last request processed by the X11 server.
• length — the length of the reply, in words. and reminder bestie: a word is 4 bytes. ✨
• xi_reply_type — TODO: NOT YET DOCUMENTED.
• num_atoms — TODO: NOT YET DOCUMENTED.

---

🌸 DESCRIPTION 🌸

okay so. the description section on this page is… literally empty. nothing. void. a blank canvas. 🕳️ the vibe is immaculate but the words are not there, and i'm not gonna invent lore that the manpage didn't give me. so we simply vibe in silence. 💀

---

⭐ RETURN VALUE ⭐

it hands you back an xcb_input_list_device_properties_cookie_t — a cookie!! 🍪 errors have to be handled when you call the reply function xcb_input_list_device_properties_reply, so don't just sit on that cookie forever.

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

---

💅 ERRORS 💅

this request does never generate any errors. not one. zero. she's perfect, she's unproblematic, she does not start drama. 💅✨

---

🎀 SEE ALSO 🎀

…nothing listed here, bestie. the section exists, the content does not. we respect her privacy. 🦋

---

🌈 AUTHOR 🌈

generated from xinput.xml. contact xcb@lists.freedesktop.org for corrections and improvements — so if you spot something sus, that's the address to slide into. 📩

---

and that's the whole page, bestie!! this little beauty came from X Version 11, libxcb 1.17.0, and it's part of the XCB Requests manual — go forth and list those device properties, you absolute icon. 🧚💜🌸