xcb_xkb_exten...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_extension_device_notify_event_t ✨

okay bestie, so this is a page from the XCB Events corner of the X world β€” it's the manual for xcb_xkb_extension_device_notify_event_t, aka the struct that shows up when an XKB extension device has ✨something✨ to tell you. Manual page name is xcb_xkb_exten...notify_event_t(3) (yes the truncation is giving very much "character limit", we love her anyway πŸ’…).


πŸ¦‹ NAME πŸ¦‹

xcb_xkb_extension_device_notify_event_t β€” literally just the event datastructure, no further notes, that's the whole name section, periodt.


🌸 SYNOPSIS 🌸

#include <xcb/xkb.h>

πŸŽ€ Event datastructure πŸŽ€

so here's the whole struct, every field, exactly as it is, no cap:

typedef struct xcb_xkb_extension_device_notify_event_t {
    uint8_t         response_type;
    uint8_t         xkbType;
    uint16_t        sequence;
    xcb_timestamp_t time;
    uint8_t         deviceID;
    uint8_t         pad0;
    uint16_t        reason;
    uint16_t        ledClass;
    uint16_t        ledID;
    uint32_t        ledsDefined;
    uint32_t        ledState;
    uint8_t         firstButton;
    uint8_t         nButtons;
    uint16_t        supported;
    uint16_t        unsupported;
    uint8_t         pad1[2];
} xcb_xkb_extension_device_notify_event_t;

πŸ’– EVENT FIELDS πŸ’–

  • response_type β€” the type of this event, and in this case it's XCB_XKB_EXTENSION_DEVICE_NOTIFY. this same field also lives inside the xcb_generic_event_t, so it's your little "which event is this" nametag when you're telling events apart from each other πŸ‘‘
  • sequence β€” the sequence number of the last request that got processed by the X11 server. the receipts, basically 🧾
  • xkbType β€” NOT YET DOCUMENTED.
  • time β€” NOT YET DOCUMENTED.
  • deviceID β€” NOT YET DOCUMENTED.
  • reason β€” NOT YET DOCUMENTED.
  • ledClass β€” NOT YET DOCUMENTED.
  • ledID β€” NOT YET DOCUMENTED.
  • ledsDefined β€” NOT YET DOCUMENTED.
  • ledState β€” NOT YET DOCUMENTED.
  • firstButton β€” NOT YET DOCUMENTED.
  • nButtons β€” NOT YET DOCUMENTED.
  • supported β€” NOT YET DOCUMENTED.
  • unsupported β€” NOT YET DOCUMENTED.
ngl bestie, the docs really said "mystery" for a whole stack of these fields 😭 the struct is serving full silhouette, the explanations are not. but like, we still love her 🫢

🌈 DESCRIPTION 🌈

okay so… this section is literally empty. no description. nothing. it's giving "we'll fill this in later" and later never came πŸ™ˆ iconic in its own way tbh.


⭐ SEE ALSO ⭐

also empty, bestie. nothing to see here. no cross-references, no siblings, just vibes πŸ¦‹


πŸ‘‘ AUTHOR πŸ‘‘

Generated from xkb.xml. Contact xcb@lists.freedesktop.org for corrections and improvements β€” so if you spot something sus, that's your hotline, fr fr πŸ’Œ


and that's the whole page, bestie! stay hydrated, read your structs carefully, and remember: the pad bytes are load-bearing πŸ’€

signing off with all the love β€” this was X Version 11, libxcb 1.17.0, and the page xcb_xkb_exten...notify_event_t(3) from the XCB Events lineup πŸŒΈπŸ’…βœ¨