xcb_input_dev...cus_in_event_t(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_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 case XCB_INPUT_DEVICE_FOCUS_OUT. this field is also present in the xcb_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: the response_type field is described as XCB_INPUT_DEVICE_FOCUS_OUT even 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 πŸ¦‹πŸ’–