xcb_input_xi_change_property(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_property — the XCB Requests girlies know her

okay so bestie, welcome to xcb_input_xi_change_property(3) 🎀 this one lives in the XCB Requests fam, and she's a request function, which is a whole vibe. lowkey she's mysterious (the docs are full of TODOs, no cap) but we're gonna walk through every single thing anyway because that's just how we do it. ✨

✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xinput.h>

🦋 Request function

here's the whole signature, character for character, don't you dare paraphrase her:

xcb_void_cookie_t xcb_input_xi_change_property(xcb_connection_t *conn,
       xcb_input_device_id_t deviceid, uint8_t mode, uint8_t format,
       xcb_atom_t property, xcb_atom_t type, uint32_t num_items, const
       void *items);

🌸 REQUEST ARGUMENTS 🌸

kay so here's every single argument and what the docs say about her. and girly, the docs say… a lot of TODO: NOT YET DOCUMENTED. 😭 not me being honest with you. i'm not gonna make up lore, so here's exactly what's on the page:

  • conn — The XCB connection to X11. 💖 your lil lifeline to the server, the main character of the whole operation.
  • deviceid — TODO: NOT YET DOCUMENTED. 🙈
  • mode — TODO: NOT YET DOCUMENTED. 🙈
  • format — TODO: NOT YET DOCUMENTED. 🙈
  • property — TODO: NOT YET DOCUMENTED. 🙈
  • type — TODO: NOT YET DOCUMENTED. 🙈
  • num_items — TODO: NOT YET DOCUMENTED. 🙈
  • items — TODO: NOT YET DOCUMENTED. 🙈
bestie i know. seven whole TODOs. it's giving "shrug emoji" but we respect the honesty of the manpage. 💀

💜 DESCRIPTION 💜

the description section is, and i say this with love, empty. nada. nothing. a blank canvas. 🎨 the manpage simply does not describe this request in prose, so i'm not about to invent behaviour that isn't there — that would be a lie and lying is not the vibe. what we do know about her is all up in the arguments and the return value, so let's keep it moving. 🫶

🔥 RETURN VALUE 🔥

she hands you back an xcb_void_cookie_t. and because she's a void cookie situation, errors (if any) have to be handled in the event loop. 👑

if you'd rather handle your errors directly with xcb_request_check instead, then use xcb_input_xi_change_property_checked. literally that's the whole point of the checked version. see xcb-requests(3) for the details, iykyk. ✨

💀 ERRORS 💀

plot twist of the century: this request does never generate any errors. not one. zero. she's unproblematic fr fr. 🌈

🦋 SEE ALSO 🦋

this section is empty on the page. nothing listed. that's it, that's the whole thing. 🎀

👑 AUTHOR 👑

Generated from xinput.xml. 📜 Contact xcb@lists.freedesktop.org for corrections and improvements.

and that's the whole page bestie, every option, every arg, every TODO, preserved exactly. no cap. 💅

X Version 11 · libxcb 1.17.0 · mwah, catch you in the next manpage, slay the house down 🌸✨🦋

📦 where this page comes from