xcb_input_xi_...lease_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_barrier_release_pointer β€” bestie edition

okay so real talk, this page lives in the XCB Requests section of the manual (you know, the xcb_input_xi_...lease_pointer(3) girlies), and it's short. like, suspiciously short. but we're gonna make it cute anyway πŸŽ€


✨ NAME ✨

xcb_input_xi_barrier_release_pointer β€” and that's it, that's the whole name, the description slot is literally empty bestie, the upstream just left it blank πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

#include <xcb/xinput.h>

Request function 🌸

xcb_void_cookie_t
       xcb_input_xi_barrier_release_pointer(xcb_connection_t *conn,
       uint32_t num_barriers, const
       xcb_input_barrier_release_pointer_info_t *barriers);

πŸ‘‘ REQUEST ARGUMENTS πŸ‘‘

  • conn β€” your XCB connection to X11. the whole portal to the server, no cap πŸ”₯
  • num_barriers β€” TODO: NOT YET DOCUMENTED. yeah. the docs said "later" and then never came back 😭 that's literally all we know fr fr.
  • barriers β€” TODO: NOT YET DOCUMENTED. same energy. it's a pointer to xcb_input_barrier_release_pointer_info_t and the description is a mystery πŸ•΅οΈβ™€οΈβœ¨
not me reading the docs and finding two whole TODOs πŸ’€ it's giving "we'll fill this in before release" and they did NOT.

🌈 DESCRIPTION 🌈

...so there's genuinely nothing here. like, the section exists and it's empty. the void. the abyss. we simply do not have a description on this one 🫢 (this is a faithful reproduction of the emptiness, bestie β€” I'm not gonna make up lore that isn't in the source ✨)


⭐ RETURN VALUE ⭐

It hands you back an xcb_void_cookie_t β€” yes, void, because this request doesn't return any data, it just does the thing πŸ’…

Any errors? You handle those in the event loop, periodt. That's the vibe.

But WAIT β€” if you'd rather handle errors directly with xcb_request_check instead, then use xcb_input_xi_barrier_release_pointer_checked and go off πŸ‘‘

See xcb-requests(3) for the details on how all that works, iykyk πŸ“š


πŸ’€ ERRORS πŸ’€

good news!! this request does never generate any errors. zero. none. a clean girl, a drama-free icon, she simply does not start problems 🌸✨


🧚 SEE ALSO 🧚

nothing listed bestie, the section's just vibing there empty πŸ™ˆ


πŸŽ€ AUTHOR πŸŽ€

Generated from xinput.xml. Got corrections or improvements? Contact xcb@lists.freedesktop.org β€” they're literally waiting for your email, go send it πŸ’Œ


X Version 11 Β· libxcb 1.17.0 β€” and that's the whole page, babes. tiny page, huge heart. mwah πŸ’‹ stay hydrated, close your connections, and may your barriers always release πŸ¦‹πŸ’–