XCB_INPUT_XI_SET_CLIENT_POINTER(3)

πŸ“¦
version 1.17.0 Β· 4 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, debian trixie, fedora 43, fedora 44, nixpkgs unstable, opensuse-leap 16.0, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’… 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 says TODO: 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 πŸ’–βœ¨πŸ¦‹