xcb_xkb_new_k...notify_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_xkb_new_keyboard_notify_event_t β€” the manual page πŸ’–

okay bestie, welcome to the xcb_xkb_new_keyboard_notify_event_t page from the XCB Events corner of the libxcb universe ✨ it's section 3 of the manual, and yes, the official one-line description after the dash is literally empty β€” the void, the silence, the blank space 🫢 so we're just gonna vibe with the name itself.


🌸 NAME 🌸

xcb_xkb_new_keyboard_notify_event_t β€” and that's it. That's the whole name. No little tagline, no nothing. It's giving "mysterious main character" energy πŸ’…


✨ SYNOPSIS ✨

first up, you gotta pull in the header:

#include <xcb/xkb.h>

πŸŽ€ Event datastructure πŸŽ€

here's the whole struct, every single field, no cap:

typedef struct xcb_xkb_new_keyboard_notify_event_t {
    uint8_t         response_type;
    uint8_t         xkbType;
    uint16_t        sequence;
    xcb_timestamp_t time;
    uint8_t         deviceID;
    uint8_t         oldDeviceID;
    xcb_keycode_t   minKeyCode;
    xcb_keycode_t   maxKeyCode;
    xcb_keycode_t   oldMinKeyCode;
    xcb_keycode_t   oldMaxKeyCode;
    uint8_t         requestMajor;
    uint8_t         requestMinor;
    uint16_t        changed;
    uint8_t         pad0[14];
} xcb_xkb_new_keyboard_notify_event_t;

look at that pad0[14] just sitting there padding it out, iconic honestly 🌈


πŸ¦‹ EVENT FIELDS πŸ¦‹

okay so here's the rundown on every field, one by one, in order, the way it deserves:

  • response_type β€” the type of this event, and in this particular case that type is XCB_XKB_NEW_KEYBOARD_NOTIFY. plot twist: this field also lives inside xcb_generic_event_t, so you can use it to tell your events apart from each other. very "which one of you is it" of it πŸ’€
  • sequence β€” the sequence number of the last request that the X11 server processed. the receipts, basically 🧾
  • xkbType β€” NOT YET DOCUMENTED. 😭
  • time β€” NOT YET DOCUMENTED. 😭
  • deviceID β€” NOT YET DOCUMENTED. 😭
  • oldDeviceID β€” NOT YET DOCUMENTED. 😭
  • minKeyCode β€” NOT YET DOCUMENTED. 😭
  • maxKeyCode β€” NOT YET DOCUMENTED. 😭
  • oldMinKeyCode β€” NOT YET DOCUMENTED. 😭
  • oldMaxKeyCode β€” NOT YET DOCUMENTED. 😭
  • requestMajor β€” NOT YET DOCUMENTED. 😭
  • requestMinor β€” NOT YET DOCUMENTED. 😭
  • changed β€” NOT YET DOCUMENTED. 😭
not me reading "NOT YET DOCUMENTED" twelve times in a row πŸ’€ the docs said "figure it out bestie" and honestly? valid. just know that's exactly what the source says, fr fr.

πŸ’œ DESCRIPTION πŸ’œ

so... there is no description text here. it's empty. the section exists, the words do not. a true minimalist moment πŸ‘‘


⭐ SEE ALSO ⭐

also empty, bestie πŸ™ˆ no cross-references, no little friends to go visit. just you and this page.


πŸ‘‘ AUTHOR πŸ‘‘

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


and that's the whole page, start to finish 🌸 it's from X Version 11, libxcb 1.17.0, and it signs off exactly like the original did, title tag and all: xcb_xkb_new_k...notify_event_t(3). slay, you made it to the end, ily, go write some XKB code πŸ’…βœ¨πŸŽ€