xcb_input_xi_warp_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_warp_pointer ✨

okay bestie, so this page is from the XCB Requests corner of the world — it's the manual for xcb_input_xi_warp_pointer, which lives in the xcb-input crew. 🦋 Buckle up, it's giving "short but mighty".

🌸 NAME 🌸

xcb_input_xi_warp_pointer — the pointer-warping request from the X Input extension, as served to you by XCB 💫

🎀 SYNOPSIS 🎀

#include <xcb/xinput.h>

💅 Request function 💅

xcb_void_cookie_t xcb_input_xi_warp_pointer(xcb_connection_t *conn,
       xcb_window_t src_win, xcb_window_t dst_win,
       xcb_input_fp1616_t src_x, xcb_input_fp1616_t src_y,
       uint16_t src_width, uint16_t src_height,
       xcb_input_fp1616_t dst_x, xcb_input_fp1616_t dst_y,
       xcb_input_device_id_t deviceid);

🌈 REQUEST ARGUMENTS 🌈

no cap, these are the little guys you gotta feed it:

  • conn — the XCB connection to X11. your whole line to the server, your main character connection 🔌
  • src_win — TODO: NOT YET DOCUMENTED. 🙈 (yeah bestie, they left it blank, I'm not gonna make stuff up)
  • dst_win — TODO: NOT YET DOCUMENTED. 🙈
  • src_x — TODO: NOT YET DOCUMENTED. 🙈
  • src_y — TODO: NOT YET DOCUMENTED. 🙈
  • src_width — TODO: NOT YET DOCUMENTED. 🙈
  • src_height — TODO: NOT YET DOCUMENTED. 🙈
  • dst_x — TODO: NOT YET DOCUMENTED. 🙈
  • dst_y — TODO: NOT YET DOCUMENTED. 🙈
  • deviceid — TODO: NOT YET DOCUMENTED. 🙈
literally the entire argument list is a mystery to the docs, bestie. the source of truth is xinput.xml and we are NOT guessing. iykyk 💀

✨ DESCRIPTION ✨

…nothing here, babe. The original page has a DESCRIPTION heading with absolutely nothing under it. That's it. That's the section. Empty. It's giving "said nothing, slayed anyway" 💅

🔥 RETURN VALUE 🔥

It hands you back an xcb_void_cookie_t. That's right — a void cookie, so there's no shiny reply data waiting for you.

Errors (if any) have to be handled in the event loop, okay? That's the whole vibe. ⭐

If you want to handle errors directly instead, with xcb_request_check, then use xcb_input_xi_warp_pointer_checked instead. Peep xcb-requests(3) for the full details on how that whole cookie situation works. 🍓

💀 ERRORS 💀

This request does never generate any errors. Not one. Zero. None. Iconic behaviour, honestly. 🫶

👑 SEE ALSO 👑

<cute>…there's nothing listed here either.</cute> The section is there, the references are not. So, respectfully: no SEE ALSO refs on this page, periodt. 🎀

💜 AUTHOR 💜

Generated from xinput.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they're the ones who want to hear it. 📬

and that's the whole page, bestie 🌸 this cutie came to you courtesy of X Version 11 and libxcb 1.17.0, from the xcb_input_xi_warp_pointer(3) page itself. go forth and warp, or don't, since half the args are TODO 💖✨

📦 where this page comes from