xcb_input_xi_change_cursor(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_change_cursor β€” the manual page, but make it make sense πŸ’–

okay so bestie, welcome to section 3 of the manual: xcb_input_xi_change_cursor. yes the name section in the original was literally blank, we're not gonna pretend otherwise. it's giving "the title said it all" energy. πŸŽ€


✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xinput.h>

πŸ¦‹ Request function

here's the whole entire vibe, one function, four arguments, no notes:

xcb_void_cookie_t xcb_input_xi_change_cursor(xcb_connection_t *conn,
       xcb_window_t window, xcb_cursor_t cursor,
       xcb_input_device_id_t deviceid);

🌸 REQUEST ARGUMENTS 🌸

  • conn β€” the XCB connection to X11. your lil hotline to the server, periodt.
  • window β€” TODO: NOT YET DOCUMENTED. yeah bestie. the docs simply never got written. not me reading a TODO in the official manpage 😭
  • cursor β€” TODO: NOT YET DOCUMENTED. same situation. iconic of them honestly.
  • deviceid β€” TODO: NOT YET DOCUMENTED. yep. still a TODO. we're all just out here living the undocumented life 🫢

πŸ’… DESCRIPTION πŸ’…

so, um. there is literally nothing here in the original. the DESCRIPTION section is empty. no prose, no lore, no context. we know what we know from the synopsis and nothing more.

the way this section is just… blank. πŸ’€ lowkey iconic, highkey unhelpful. but we're being honest about it instead of making stuff up, because that's the rule.


⭐ RETURN VALUE ⭐

it hands you back an xcb_void_cookie_t. that's the whole thing.

and listen β€” any errors? they have to be handled over in the event loop. that's just how void requests roll around here. πŸŒ€

if you'd rather catch errors directly, no event-loop side quest required, then you want xcb_request_check and you want the _checked variant instead:

xcb_input_xi_change_cursor_checked

more deets on all that over in xcb-requests(3). go read it, i'll wait. πŸ“


πŸ’€ ERRORS πŸ’€

not a single one. this request never generates any errors. zero. none. no cap.

that's what the page says, bestie β€” "This request does never generate any errors." take it at face value and go be free. ✨

πŸ”₯ SEE ALSO πŸ”₯

the original page lists this heading and then… nothing under it. empty. a whole section with zero references. the audacity, honestly. πŸ™ˆ

(though xcb-requests(3) did get name-dropped up in RETURN VALUE, so that one's the real one to know about. 😌)


πŸ‘‘ AUTHOR πŸ‘‘

generated from xinput.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who wanna hear it. πŸ“§


🧚 the cute sign-off 🧚

and that's the whole page, bestie!! this beauty comes from X Version 11, libxcb 1.17.0, and it lives its best life as xcb_input_xi_change_cursor(3). go forth, change some cursors, stay documented (unlike some of these arguments πŸ’œ). mwah. πŸŒˆπŸ’–βœ¨