xcb_input_dev...cus_in_event_t(3)
π xcb_input_dev...cus_in_event_t(3) π
okay bestie, welcome to the manual page for xcb_input_dev...cus_in_event_t(3) from the XCB Events crew π¦ this is one of those little event datastructures that lives in libxcb, and honestly? she's giving "quiet but essential". let's get into it β¨
πΈ NAME πΈ
xcb_input_device_focus_in_event_t β that's it, that's the name π
(the original page literally leaves it blank after the dash, so we're not gonna invent lore that isn't there, no cap)
β¨ SYNOPSIS β¨
first things first, you gotta pull her in:
#include <xcb/xinput.h>
π Event datastructure π
here's the whole glow-up, field by field:
typedef struct xcb_input_device_focus_in_event_t {
uint8_t response_type;
uint8_t detail;
uint16_t sequence;
xcb_timestamp_t time;
xcb_window_t window;
uint8_t mode;
uint8_t device_id;
uint8_t pad0[18];
} xcb_input_device_focus_in_event_t;
look at her. structured. iconic. and yes, that pad0[18] is just padding doing its little job in the background, we respect her π
π EVENT FIELDS π
here's the breakdown, one field at a time, no skips, fr fr:
response_typeβ the type of this event, in this caseXCB_INPUT_DEVICE_FOCUS_OUT. this field is also present in thexcb_generic_event_t, and it's the thing you use to tell events apart from each other. vibe check: it's your event ID card π³sequenceβ the sequence number of the last request processed by the X11 server. tracking number energy π¦detailβNOT YET DOCUMENTED.π bestie the docs said "figure it out"timeβNOT YET DOCUMENTED.πwindowβNOT YET DOCUMENTED.πmodeβNOT YET DOCUMENTED.πdevice_idβNOT YET DOCUMENTED.π
not me listing five whole fields that are literally just NOT YET DOCUMENTED. π keeping it real, that's exactly what the page says, so that's exactly what you get. no inventing, no guessing, periodt.
π DESCRIPTION π
she's empty. the original page has a DESCRIPTION section with absolutely nothing under it. a true minimalist. main character silence. π
π SEE ALSO π
also empty!! no cross-references, no little friends to link to. she stands alone. independent queen behavior π
π«Ά AUTHOR π«Ά
Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (so if something's wrong, that's who you email, don't come for me π)
β tiny note before you go: theresponse_typefield is described asXCB_INPUT_DEVICE_FOCUS_OUTeven though this whole struct is named..._focus_in_event_t. that's what the page says, character for character, so I'm passing it straight to you with zero editing. iykyk π€«
okay that's the whole page bestie, you now know everything this manual knows (which, in the DESCRIPTION department, is nothing, and that's valid π
). stay curious, read your headers, and hydrate πβ¨
X Version 11 Β· libxcb 1.17.0 β mwah, that's the version and the source, catch you on the next page π¦π
π¦ 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