xcb_input_cha...vice_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

✨ NAME ✨

xcb_input_change_device_property β€” bestie it literally changes a device property, that's the whole vibe πŸ’… (the manpage itself leaves the description blank, so we're working with what we got, no cap)


🌸 SYNOPSIS 🌸

okay so first you gotta pull in the header:

#include <xcb/xinput.h

Request function

xcb_void_cookie_t
       xcb_input_change_device_property(xcb_connection_t *conn,
       xcb_atom_t property, xcb_atom_t type, uint8_t device_id,
       uint8_t format, uint8_t mode, uint32_t num_items, const
       void *items);

that's the whole signature, copy it exactly, don't be cute with it πŸŽ€


πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” The XCB connection to X11. it's your lil phone line to the X server, you need it for everything fr fr
  • property β€” TODO: NOT YET DOCUMENTED. yeah bestie, the docs just... didn't. it's giving mysterious. πŸ™ˆ
  • type β€” TODO: NOT YET DOCUMENTED. same energy, nobody wrote it down 😭
  • device_id β€” TODO: NOT YET DOCUMENTED. the docs left us on read πŸ’€
  • format β€” TODO: NOT YET DOCUMENTED. unbothered, undocumented, iconic
  • mode β€” TODO: NOT YET DOCUMENTED. we simply do not know, and that's the tea πŸ“
  • num_items β€” TODO: NOT YET DOCUMENTED. a mystery wrapped in a request
  • items β€” TODO: NOT YET DOCUMENTED. the plot twist we never got
not me reading the same "TODO: NOT YET DOCUMENTED" eight times 😭 the manpage authors said "figure it out" and honestly? valid but rude

πŸ’– DESCRIPTION πŸ’–

nothing here. the original page has literally nothing in this section. it's an empty room. a blank canvas. the silence is deafening 🫢 but hey, at least it's honest about it


✨ RETURN VALUE ✨

it hands you back an xcb_void_cookie_t. and like β€” errors (if any) have to be handled in the event loop, so you can't just ignore the cookie and walk away, bestie, that's not the move.

if you'd rather handle errors directly with xcb_request_check instead, then use xcb_input_change_device_property_checked β€” that's the checked twin, the responsible sibling. see xcb-requests(3) for details πŸ‘‘


πŸŽ€ ERRORS πŸŽ€

This request does never generate any errors.

read that again. never. zero. none. no drama, no error codes, no little surprises waiting for you. she's a peaceful queen 🌈✨


⭐ SEE ALSO ⭐

...nothing listed. the section exists, it's just vibing there, empty, main character energy with no supporting cast πŸ’€


πŸ‘‘ AUTHOR πŸ‘‘

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

so if something's wrong, that's who you email β€” not me, I'm just the messenger 🧚


and that's the whole page, bestie!! πŸ’œ this one came from X Version 11, libxcb 1.17.0, and the page is xcb_input_cha...vice_property(3) β€” go forth and change those device properties, slay, periodt πŸŽ€πŸ¦‹πŸ’–