XCB_INPUT_XI_GET_CLIENT_POINTER_UNCHECKED(3)
π xcb_input_xi_get_client_pointer β the manual page bestie
okay so this is xcb_input_xi_get_client_pointer(3), part of the XCB request family, and yes the name is a whole mouthful but we move π«Ά
β¨ NAME β¨
xcb_input_xi_get_client_pointer β no description attached, the original page literally just leaves this one blank, and honestly? mysterious. iconic. we respect it. π
πΈ SYNOPSIS πΈ
first things first, you gotta bring in the header:
#include <xcb/xinput.h>
π Request function
xcb_input_xi_get_client_pointer_cookie_t
xcb_input_xi_get_client_pointer(xcb_connection_t *conn,
xcb_window_t window);
π¦ Reply datastructure
typedef struct xcb_input_xi_get_client_pointer_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint8_t set;
uint8_t pad1;
xcb_input_device_id_t deviceid;
uint8_t pad2[20];
} xcb_input_xi_get_client_pointer_reply_t;
π Reply function
xcb_input_xi_get_client_pointer_reply_t
*xcb_input_xi_get_client_pointer_reply(xcb_connection_t *conn,
xcb_input_xi_get_client_pointer_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil phone line to the server, she's doing the talking π¬windowβTODO: NOT YET DOCUMENTED.bestie they really just left this one blank, it's giving "we'll finish it later" and later never came π
π REPLY FIELDS π
response_typeβ the type of this reply, which in this case isXCB_INPUT_XI_GET_CLIENT_POINTER. this field also lives insidexcb_generic_reply_t, and that's how you tell your replies apart from each other β very "which one of y'all is this" energy πsequenceβ the sequence number of the last request processed by the X11 server. basically the receipt number π§Ύlengthβ the length of the reply, measured in words (and a word here is4bytes, no cap) πsetβTODO: NOT YET DOCUMENTED.πdeviceidβTODO: NOT YET DOCUMENTED.π
π DESCRIPTION π
this section is empty in the original. literally nothing. a blank canvas. we're leaving it exactly as the universe intended β¨ (the vibe check came back: no info π)
β RETURN VALUE β
you get back an xcb_input_xi_get_client_pointer_cookie_t. that's a cookie, and cookies mean the actual answer isn't here yet β you gotta go pick it up later πͺ
so: errors have to be handled when you call the reply function, xcb_input_xi_get_client_pointer_reply.
but if you'd rather handle your errors inside the event loop instead, use xcb_input_xi_get_client_pointer_unchecked β and go peek at xcb-requests(3) for the full deets on how that works.
π ERRORS π
good news bestie: this request does never generate any errors. not one. zero. a peaceful queen π
π SEE ALSO π
nothing here either. the original page left this one blank. we're not gonna invent references, that's not the move π
π AUTHOR π
Generated from xinput.xml. For corrections and improvements, contact xcb@lists.freedesktop.org β they're the ones to @ in the group chat π§
and that's the whole page, fr fr. go forth, call your function, collect your cookie π
X Version 11 Β· libxcb 1.17.0 β that's the source and version info from the footer, folded in right here at the end because we're cute like that πβ¨π
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms