xcb_render_create_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_render_create_cursor ✨

okay bestie, gather round, because today we're looking at xcb_render_create_cursor, a lil function from the XCB crew (that's the X protocol binding situation, iykyk) πŸ’…


🌸 NAME 🌸

xcb_render_create_cursor β€”

that's it. that's the name. the description after the dash is literally empty, no cap, the manpage just left it blank like a read receipt πŸ™ˆ so we're all just gonna have to vibe with the mystery.


πŸŽ€ SYNOPSIS πŸŽ€

First things first, you gotta bring the header in:

#include <xcb/render.h>

πŸ’– Request function πŸ’–

xcb_void_cookie_t xcb_render_create_cursor(xcb_connection_t *conn,
       xcb_cursor_t cid, xcb_render_picture_t source, uint16_t x,
       uint16_t y);

look at her. five args and a xcb_void_cookie_t return. she's serving structure, she's serving types, she's iconic πŸ‘‘


πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11. your whole lifeline to the server, the group chat with the X server if you will πŸ’Œ
  • cid β€” TODO: NOT YET DOCUMENTED. yeah. the docs said "we'll get to it" and then never did 😭
  • source β€” TODO: NOT YET DOCUMENTED. also a mystery bestie, also a mystery 🫢
  • x β€” TODO: NOT YET DOCUMENTED. it's giving "placeholder" energy fr fr
  • y β€” TODO: NOT YET DOCUMENTED. same situation, we simply do not know πŸ“
not me reading four whole TODOs in a row πŸ’€ the manpage really said "figure it out"

🌈 DESCRIPTION 🌈

...nothing. absolutely nothing. the DESCRIPTION section is empty, bestie. a blank canvas. main character energy but make it silent ✨


πŸ’œ RETURN VALUE πŸ’œ

She hands you back an xcb_void_cookie_t. That's it, that's the tea β˜•

Any errors (if there even are any, which β€” spoiler β€” there aren't, keep reading) have to be handled over in the event loop. That's just how the async girlies operate.

But wait, if you'd rather deal with errors directly, right there, no event loop nonsense, then use xcb_render_create_cursor_checked instead. Head over to xcb-requests(3) for all the deets on how that whole checked-vs-unchecked situation works πŸ“š


πŸ”₯ ERRORS πŸ”₯

This request does never generate any errors.

periodt. zero errors. none. she's flawless, she's unbothered, she's never once caused a problem πŸ’…βœ¨


⭐ SEE ALSO ⭐

crickets πŸ¦—

yeah there's literally nothing listed here. the see-also section said "no thoughts, head empty." iconic behaviour honestly.


πŸ‘‘ AUTHOR πŸ‘‘

Generated from render.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're the ones taking feedback, not me 🫢


and that's the whole page bestie!! πŸ’– this was X Version 11, libxcb 1.17.0, and yeah the date is just sitting there in the footer like a timestamp on a story you forgot to archive 🌸 stay hydrated, go create some cursors, mwah πŸ˜˜πŸŽ€