xcb_input_cha...vice_property(3)
β¨ 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 frpropertyβ 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, iconicmodeβ 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 requestitemsβ 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 ππ¦π
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms