xcb_xkb_map_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_map_notify_event_t ✨

okay so bestie, welcome to the manual page for xcb_xkb_map_notify_event_t, which lives in section 3 of the manual (that's the library-functions girlies πŸ’…). It's part of XCB Events, and it's giving "struct that shows up when the X server has keyboard map tea to spill." Let's get into it 🫢


🌸 NAME 🌸

xcb_xkb_map_notify_event_t β€” no description line, bestie. The original page literally just leaves it blank after the dash. It's mysterious. It's giving main character energy with no backstory. πŸ’€


πŸŽ€ SYNOPSIS πŸŽ€

First things first, you gotta pull in the header:

#include <xcb/xkb.h>

πŸ¦‹ Event datastructure πŸ¦‹

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

typedef struct xcb_xkb_map_notify_event_t {
    uint8_t         response_type;
    uint8_t         xkbType;
    uint16_t        sequence;
    xcb_timestamp_t time;
    uint8_t         deviceID;
    uint8_t         ptrBtnActions;
    uint16_t        changed;
    xcb_keycode_t   minKeyCode;
    xcb_keycode_t   maxKeyCode;
    uint8_t         firstType;
    uint8_t         nTypes;
    xcb_keycode_t   firstKeySym;
    uint8_t         nKeySyms;
    xcb_keycode_t   firstKeyAct;
    uint8_t         nKeyActs;
    xcb_keycode_t   firstKeyBehavior;
    uint8_t         nKeyBehavior;
    xcb_keycode_t   firstKeyExplicit;
    uint8_t         nKeyExplicit;
    xcb_keycode_t   firstModMapKey;
    uint8_t         nModMapKeys;
    xcb_keycode_t   firstVModMapKey;
    uint8_t         nVModMapKeys;
    uint16_t        virtualMods;
    uint8_t         pad0[2];
} xcb_xkb_map_notify_event_t;

πŸ’– EVENT FIELDS πŸ’–

  • response_type β€” the type of this event, which in this case is XCB_XKB_MAP_NOTIFY. Bestie, this same field also lives inside xcb_generic_event_t, so you can use it to tell your events apart from each other. It's the little name tag at the party. πŸŽ€
  • sequence β€” the sequence number of the last request processed by the X11 server. Slay, tracking. ✨
  • xkbType β€” NOT YET DOCUMENTED. πŸ’€
  • time β€” NOT YET DOCUMENTED. πŸ’€
  • deviceID β€” NOT YET DOCUMENTED. πŸ’€
  • ptrBtnActions β€” NOT YET DOCUMENTED. πŸ’€
  • changed β€” NOT YET DOCUMENTED. πŸ’€
  • minKeyCode β€” NOT YET DOCUMENTED. πŸ’€
  • maxKeyCode β€” NOT YET DOCUMENTED. πŸ’€
  • firstType β€” NOT YET DOCUMENTED. πŸ’€
  • nTypes β€” NOT YET DOCUMENTED. πŸ’€
  • firstKeySym β€” NOT YET DOCUMENTED. πŸ’€
  • nKeySyms β€” NOT YET DOCUMENTED. πŸ’€
  • firstKeyAct β€” NOT YET DOCUMENTED. πŸ’€
  • nKeyActs β€” NOT YET DOCUMENTED. πŸ’€
  • firstKeyBehavior β€” NOT YET DOCUMENTED. πŸ’€
  • nKeyBehavior β€” NOT YET DOCUMENTED. πŸ’€
  • firstKeyExplicit β€” NOT YET DOCUMENTED. πŸ’€
  • nKeyExplicit β€” NOT YET DOCUMENTED. πŸ’€
  • firstModMapKey β€” NOT YET DOCUMENTED. πŸ’€
  • nModMapKeys β€” NOT YET DOCUMENTED. πŸ’€
  • firstVModMapKey β€” NOT YET DOCUMENTED. πŸ’€
  • nVModMapKeys β€” NOT YET DOCUMENTED. πŸ’€
  • virtualMods β€” NOT YET DOCUMENTED. πŸ’€
ngl the docs are NOT documenting here. Like, twenty-three fields of pure mystery. We love a cryptic queen but this is a lot πŸ™ˆ

πŸ”₯ DESCRIPTION πŸ”₯

Nothing. Empty. Void. The description section is giving absolutely nothing and honestly? Iconic. Do not perceive it. 😭


🌈 SEE ALSO 🌈

Also empty, bestie. No cross-references. No friends. Just vibes. πŸ¦‹


πŸ‘‘ AUTHOR πŸ‘‘

Generated from xkb.xml. If you want corrections and improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who actually want to hear it. πŸ’Œ


and that's the whole page, bestie!! 🫢 this one comes to you from X Version 11, libxcb 1.17.0 β€” periodt, no cap, go forth and handle your map notify events πŸ’…βœ¨πŸ’–