XCB_INPUT_XI_SET_CLIENT_POINTER_CHECKED(3)
π xcb_input_xi_set_client_pointer β the XCB Requests girlies' guide β¨
okay so bestie, welcome to the manual page for xcb_input_xi_set_client_pointer(3) from the XCB Requests collection π yes it's a whole vibe, yes it lives in section 3 of your man pages, and yes we're gonna get through it together. grab a strawberry π and let's go.
β¨ NAME β¨
xcb_input_xi_set_client_pointer β and that's literally it, no cap, the original gave us nothing else to work with here π
πΈ SYNOPSIS πΈ
first things first, you gotta pull in the header:
#include <xcb/xinput.h>
π¦ Request function π¦
here's the function signature, character for character, no notes:
xcb_void_cookie_t
xcb_input_xi_set_client_pointer(xcb_connection_t *conn,
xcb_window_t window, xcb_input_device_id_t deviceid);
she's giving "short and mysterious" energy and honestly? iconic. π
π REQUEST ARGUMENTS π
here's the tea on each argument, one by one:
connβ this is your XCB connection to X11. your lil lifeline to the server, your main character connection, the whole reason any of this works π«Άwindowβ um. so. the original saysTODO: NOT YET DOCUMENTED.and I'm just the messenger bestie π like, it's giving unfinished homework but we're respecting the lore.deviceidβ same situation fr fr,TODO: NOT YET DOCUMENTED.so mysterious of it π
π DESCRIPTION π
okay so lowkey... the DESCRIPTION section of this page is empty. like, completely. nothing. a void. and the way that I have to faithfully tell you that instead of making something up is a whole test of my character π the facts are the facts, bestie.
β RETURN VALUE β
so what do you get back? an xcb_void_cookie_t. that's it. that's the return.
any errors (if there even are any) have to be handled over in the event loop β you don't get them handed to you directly here. periodt.
but wait, there's options π if you'd rather handle errors directly with xcb_request_check instead, then you want to use xcb_input_xi_set_client_pointer_checked. and if you want the full rundown on how all this request/cookie business works, go read xcb-requests(3). it's the syllabus, read it.
π ERRORS π
get this β this request does never generate any errors. zero. none. flawless behaviour, no drama, she just shows up and does her job. we love a low-maintenance queen π
π₯ SEE ALSO π₯
bestie... there's nothing here. the SEE ALSO section is empty. I know. I'm as shook as you are. nothing to cross-reference, nowhere to go next. just vibes πβ¨
π AUTHOR π
this page was 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 the ones holding the pen, so slide into their inbox, not mine π«Ά
and that's a wrap on our little journey, babe π this page came to you from X Version 11, libxcb 1.17.0 β so yeah, shoutout to the version, shoutout to the date, shoutout to xcb_input_xi_...client_pointer(3) for keeping it real. now go forth and set that client pointer, you absolute legend πβ¨π¦
π¦ 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