xcb_focus_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_focus_in_event_t πŸŽ€

okay bestie, we're diving into the XCB events part of the libxcb manual, page xcb_focus_in_event_t(3). it's a struct page. it's short. it's lowkey mysterious. let's go πŸ’…


✨ NAME ✨

xcb_focus_in_event_t β€” NOT YET DOCUMENTED πŸ™ˆ

yes, that's it. that's the whole name line. the maintainers really said "figure it out yourself" and honestly? iconic of them.


🌸 SYNOPSIS 🌸

#include <xcb/xproto.h>

πŸ¦‹ Event datastructure

typedef struct xcb_focus_in_event_t {
    uint8_t      response_type;
    uint8_t      detail;
    uint16_t     sequence;
    xcb_window_t event;
    uint8_t      mode;
    uint8_t      pad0[3];
} xcb_focus_in_event_t;

look at her. five real fields and a little padding bestie pad0[3] just vibing at the end to keep things aligned ✨


πŸ’– EVENT FIELDS πŸ’–

  • response_type β€” the type of this event, and in this case it's XCB_FOCUS_OUT. this field is also chillin' in the xcb_generic_event_t, so you can use it to tell your events apart from each other. yes, literally the field that separates one event from another. main character energy fr fr πŸ‘‘
  • sequence β€” the sequence number of the last request that got processed by the X11 server. it's the receipt number of the group chat, basically 🧾
  • detail β€” nothing. the manpage just... leaves this one blank. no description, no crumbs, not a single word. the void stares back πŸ’€
  • event β€” the window that the focus event was generated on. this is the window the X server uses to report the event to you, so it's the one you're gonna be looking at πŸͺŸ
  • mode β€” also nothing. blank. empty. a mystery wrapped in a uint8_t. we simply don't know and the page isn't gonna tell us 😭

🌈 DESCRIPTION 🌈

nothing here either, bestie. the DESCRIPTION section is empty. no prose, no lore, no tea. we move 🫢

⭐ SEE ALSO ⭐

  • xcb_generic_event_t(3)

go read that one if you want the generic event tea β€” it's where response_type hangs out, iykyk πŸ’œ


πŸ‘‘ AUTHOR πŸ‘‘

generated from xproto.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're literally asking for your notes, so don't be shy, bestie 🫢


and that's the whole page!! this beauty ships with X Version 11, libxcb 1.17.0, and the footer date stamp on the original is from the libxcb 1.17.0 release cycle. thanks for reading my little struct talk, mwah πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’