XCB_INPUT_DEVICE_PROPERTY_NOTIFY_EVENT_T(3)
π xcb_input_device_property_notify_event_t(3) π
okay bestie, gather round, because we're talking about a whole event datastructure from XCB Events β specifically xcb_input_device_property_notify_event_t. it's giving "your device's property changed and the server is texting you about it." no cap. π
β¨ NAME β¨
xcb_input_device_property_notify_event_t β that's it, that's the name, that's the whole vibe π
πΈ SYNOPSIS πΈ
first things first, you gotta let it in:
#include <xcb/xinput.h>
π¦ Event datastructure π¦
here's the glow-up, the whole struct, every single field, untouched and iconic:
typedef struct xcb_input_device_property_notify_event_t {
uint8_t response_type;
uint8_t state;
uint16_t sequence;
xcb_timestamp_t time;
xcb_atom_t property;
uint8_t pad0[19];
uint8_t device_id;
} xcb_input_device_property_notify_event_t;
yes bestie, pad0[19] is just sitting there doing nothing and honestly? same. β¨
π₯ EVENT FIELDS π₯
response_typeβ this is the type of this event, and in this case it'sXCB_INPUT_DEVICE_PROPERTY_NOTIFY. it also shows up in thexcb_generic_event_t, so you can use it to tell your events apart from each other. lowkey the social security number of events π«Άsequenceβ the sequence number of the last request processed by the X11 server. iykyk.stateβNOT YET DOCUMENTED.π yeah. it said what it said.timeβNOT YET DOCUMENTED.πpropertyβNOT YET DOCUMENTED.πdevice_idβNOT YET DOCUMENTED.π
bestie, i need you to know that i am not gatekeeping here β four of these fields are genuinely, officially, "NOT YET DOCUMENTED." in the source. i'm just the messenger. π§
π DESCRIPTION π
there is none. the description section is empty. it's giving silence, it's giving mystery, it's giving main character energy with no dialogue. β¨
π SEE ALSO π
also empty. no friends listed. this event is booked and busy and apparently alone. π
π AUTHOR π
Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes, that's the actual address, go tell them things, they're literally asking π«Ά)
and that's the whole page, bestie! π this one shipped with X Version 11 and libxcb 1.17 β so when you're out here handling your input device property notify events, that's who you thank. slay, periodt, and may your response_type always be XCB_INPUT_DEVICE_PROPERTY_NOTIFY. πβ¨π¦
π¦ 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