xcb_input_dev...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_input_device_mapping_notify_event_t πŸ’–

okay bestie, we're deep in the XCB Events section of the manual, and today's main character is xcb_input_dev...notify_event_t β€” specifically the xcb_input_device_mapping_notify_event_t ✨. It's giving "struct with a mystery backstory" and honestly? We're obsessed. Let's get into it 🫢


🌸 SYNOPSIS 🌸

First things first, you gotta bring in the header or nothing works, no cap:

#include <xcb/xinput.h>

πŸŽ€ Event datastructure

Here's the whole glow-up, exactly as it lives in the wild:

typedef struct xcb_input_device_mapping_notify_event_t {
    uint8_t              response_type;
    uint8_t              device_id;
    uint16_t             sequence;
    uint8_t              request;
    xcb_input_key_code_t first_keycode;
    uint8_t              count;
    uint8_t              pad0;
    xcb_timestamp_t      time;
    uint8_t              pad1[20];
} xcb_input_device_mapping_notify_event_t;

✨ EVENT FIELDS ✨

every field is a lil icon in its own right, let's do a vibe check on each one πŸ’…

  • response_type β€” the type of this event, and in this case it's literally XCB_INPUT_DEVICE_MAPPING_NOTIFY. plot twist: this field also shows up in the xcb_generic_event_t, so you can use it to tell your events apart from each other. very "which one of y'all is this" energy πŸ‘‘
  • sequence β€” the sequence number of the last request processed by the X11 server. the receipts, basically 🧾
  • device_id β€” NOT YET DOCUMENTED. the mystery. the enigma. we don't know her yet 😭
  • request β€” NOT YET DOCUMENTED. same boat, babe πŸ™ˆ
  • first_keycode β€” NOT YET DOCUMENTED. the docs are leaving us on read πŸ’€
  • count β€” NOT YET DOCUMENTED. it counts, allegedly πŸ’…
  • time β€” NOT YET DOCUMENTED. no timestamps for the timestamps field, ironic πŸ•
ngl, a lot of these are "NOT YET DOCUMENTED" β€” that's not me being shady, that's literally what the manpage says. it's canon, bestie. don't @ me 🌸

πŸ¦‹ DESCRIPTION πŸ¦‹

...and that's it. The DESCRIPTION section is empty. iconic behavior honestly. it said "I contain multitudes" and then contained zero words πŸ’œ


🌈 SEE ALSO 🌈

Nothing here either, bestie. The SEE ALSO section is a quiet little void. Sometimes a girl just doesn't have references ✨


πŸŽ€ AUTHOR πŸŽ€

This page was generated from xinput.xml. If you spot something that needs fixing or improving, hit up xcb@lists.freedesktop.org β€” they're the ones who take corrections and improvements 🫢


and that's the whole page, periodt πŸ’… generated from xinput.xml with love, coming to you from X Version 11 and libxcb 1.17.0 β€” stay slay, stay documented, and may all your events be told apart correctly πŸŒŸπŸ’–βœ¨