xcb_change_pointer_control(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_change_pointer_control — the XCB Requests era, bestie 💖

okay so this one lives in section 3 of the XCB Requests manual, and honestly? it's giving ✨pointer vibes✨. Let's get into it.

🎀 NAME 🎀

xcb_change_pointer_control —

(yeah bestie, that's it. the description slot is empty. the manpage said 💅 and moved on. no cap.)

🌸 SYNOPSIS 🌸

First you gotta pull in the header:

#include <xcb/xproto.h>

✨ Request function ✨

xcb_void_cookie_t xcb_change_pointer_control(xcb_connection_t *conn,
       int16_t acceleration_numerator, int16_t acceleration_denominator,
       int16_t threshold, uint8_t do_acceleration,
       uint8_t do_threshold);

look at that signature. iconic. 🫶

🦋 REQUEST ARGUMENTS 🦋

  • conn — the XCB connection to X11. your link to the mothership, your group chat with the server, the whole vibe. 🔥
  • acceleration_numerator — TODO: NOT YET DOCUMENTED. (not me being left on read by the docs 😭)
  • acceleration_denominator — TODO: NOT YET DOCUMENTED. (same, bestie, same 💀)
  • threshold — TODO: NOT YET DOCUMENTED. (the mystery continues 🙈)
  • do_acceleration — TODO: NOT YET DOCUMENTED. (unwritten, but we stan anyway 💜)
  • do_threshold — TODO: NOT YET DOCUMENTED. (the last of the undocumented girlies 🎀)
fr fr: every single one of those five arguments literally says "TODO: NOT YET DOCUMENTED." in the source page. i'm not hiding lore from you, there just isn't any. 💀

🌈 DESCRIPTION 🌈

...nothing. the DESCRIPTION section is empty. it's giving silent treatment. it's giving "read the room". zero words, maximum mystery. 🧚

👑 RETURN VALUE 👑

You get back an xcb_void_cookie_t. and here's the tea: errors (if any) have to be handled in the event loop. you don't just get them handed to you, bestie, you gotta go get them. 💅

But wait — if you'd rather handle errors directly with xcb_request_check instead, then use xcb_change_pointer_control_checked. that's your girl for the direct route. see xcb-requests(3) for the details. ⭐

💀 ERRORS 💀

okay so this is the good news section: this request does never generate any errors.

not a single one. zero. none. the drama-free request. slay. 🔥

💜 SEE ALSO 💜

...it's empty. nothing to see, nothing to also. the void. 🕳️✨

🍓 AUTHOR 🍓

Generated from xproto.xml. For corrections and improvements, contact xcb@lists.freedesktop.org — like, actually email them, they're nice, that's literally what the address is for. 📧🫶

and that's the whole page, bestie!! 💖 this came to you straight from X Version 11, running libxcb 1.17.0, filed under xcb_change_pointer_control(3). go change some pointer control, main character. periodt. 💅✨🌈

📦 where this page comes from