xcb_input_xi_query_pointer(3)

💖 xcb_input_xi_query_pointer 💖

okay bestie, welcome to the manual page for xcb_input_xi_query_pointer, straight outta XCB Requests ✨ this is the one that asks the X server "hey girl, where's the pointer at tho?" 🦋

---

✨ NAME ✨

xcb_input_xi_query_pointer — no description yet, the original page literally leaves this blank 💀

---

🎀 SYNOPSIS 🎀

#include <xcb/xinput.h>

🌸 Request function 🌸

xcb_input_xi_query_pointer_cookie_t
       xcb_input_xi_query_pointer(xcb_connection_t *conn,
       xcb_window_t window, xcb_input_device_id_t deviceid);

🦋 Reply datastructure 🦋

typedef struct xcb_input_xi_query_pointer_reply_t {
    uint8_t                   response_type;
    uint8_t                   pad0;
    uint16_t                  sequence;
    uint32_t                  length;
    xcb_window_t              root;
    xcb_window_t              child;
    xcb_input_fp1616_t        root_x;
    xcb_input_fp1616_t        root_y;
    xcb_input_fp1616_t        win_x;
    xcb_input_fp1616_t        win_y;
    uint8_t                   same_screen;
    uint8_t                   pad1;
    uint16_t                  buttons_len;
    xcb_input_modifier_info_t mods;
    xcb_input_group_info_t    group;
} xcb_input_xi_query_pointer_reply_t;

💅 Reply function 💅

xcb_input_xi_query_pointer_reply_t
       *xcb_input_xi_query_pointer_reply(xcb_connection_t *conn,
       xcb_input_xi_query_pointer_cookie_t cookie,
       xcb_generic_error_t **e);

🌈 Reply accessors 🌈

uint32_t *xcb_input_xi_query_pointer_buttons(const
       xcb_input_xi_query_pointer_request_t *reply);

int xcb_input_xi_query_pointer_buttons_length(const
       xcb_input_xi_query_pointer_reply_t *reply);

xcb_generic_iterator_t xcb_input_xi_query_pointer_buttons_end(const
       xcb_input_xi_query_pointer_reply_t *reply);

yes bestie, that first accessor really does say xcb_input_xi_query_pointer_request_t while the other two say xcb_input_xi_query_pointer_reply_t — i'm just reporting what's on the page, no editing, periodt 💅

---

💜 REQUEST ARGUMENTS 💜

• conn — your XCB connection to X11 obvs, the lil string connecting you to the server 🧵
• window — TODO: NOT YET DOCUMENTED. 🙈 yeah girl, they left this one blank
• deviceid — TODO: NOT YET DOCUMENTED. 💀 also blank, iconic of them

---

🌟 REPLY FIELDS 🌟

• response_type — the type of this reply, and in this case it's XCB_INPUT_XI_QUERY_POINTER. this field is also chillin' in the xcb_generic_reply_t, so you can use it to tell replies apart from each other 👀
• sequence — the sequence number of the last request processed by the X11 server 🔢
• length — the length of the reply, in words (and a word is 4 bytes, fyi)
• root — TODO: NOT YET DOCUMENTED. 😭
• child — TODO: NOT YET DOCUMENTED. 😭
• root_x — TODO: NOT YET DOCUMENTED. 😭
• root_y — TODO: NOT YET DOCUMENTED. 😭
• win_x — TODO: NOT YET DOCUMENTED. 😭
• win_y — TODO: NOT YET DOCUMENTED. 😭
• same_screen — TODO: NOT YET DOCUMENTED. 😭
• buttons_len — TODO: NOT YET DOCUMENTED. 😭
• mods — TODO: NOT YET DOCUMENTED. 😭
• group — TODO: NOT YET DOCUMENTED. 😭

---

🫶 DESCRIPTION 🫶

literally nothing here bestie, the DESCRIPTION section is empty. we move 🚶♀️

---

⭐ RETURN VALUE ⭐

Returns an xcb_input_xi_query_pointer_cookie_t 🍪 and heads up: errors have to be handled when you call the reply function xcb_input_xi_query_pointer_reply.

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

---

🔥 ERRORS 🔥

This request does never generate any errors. not one. zero. clean sheet. slay 💅

---

👑 SEE ALSO 👑

(this section is empty in the original — no references, no friends, just vibes)

---

🌸 AUTHOR 🌸

Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements 📧

---

and that's the whole page, bestie!! this one came to you from X Version 11 and libxcb 1.17.0 💖 thanks for reading the docs with me, go forth and query those pointers, mwah 🎀✨🦋