xcb_input_key_press_event_t(3)

💖 xcb_input_key_press_event_t 💖

okay so bestie, we're in the XCB Events part of the manual, and this whole page is about xcb_input_key_press_event_t — yes, the title is literally the whole name and the description slot is empty, no cap, that's just how this page ships. 🫶

---

✨ NAME ✨

xcb_input_key_press_event_t — and that's it. that's the name. the description field is giving void, giving nothing, giving blank. iconic of it honestly. 💅

---

🌸 SYNOPSIS 🌸

first things first, you gotta pull in the header:

#include <xcb/xinput.h>

🦋 Event datastructure 🦋

here's the whole struct, exactly as it is, don't touch a single character of it:

typedef struct xcb_input_key_press_event_t {
    uint8_t                   response_type;
    uint8_t                   extension;
    uint16_t                  sequence;
    uint32_t                  length;
    uint16_t                  event_type;
    xcb_input_device_id_t     deviceid;
    xcb_timestamp_t           time;
    uint32_t                  detail;
    xcb_window_t              root;
    xcb_window_t              event;
    xcb_window_t              child;
    uint32_t                  full_sequence;
    xcb_input_fp1616_t        root_x;
    xcb_input_fp1616_t        root_y;
    xcb_input_fp1616_t        event_x;
    xcb_input_fp1616_t        event_y;
    uint16_t                  buttons_len;
    uint16_t                  valuators_len;
    xcb_input_device_id_t     sourceid;
    uint8_t                   pad0[2];
    uint32_t                  flags;
    xcb_input_modifier_info_t mods;
    xcb_input_group_info_t    group;
} xcb_input_key_press_event_t;

look at that. so many fields. main character struct energy fr fr. 💜

---

🎀 EVENT FIELDS 🎀

okay so here's the tea on every single field, one by one, no skipping, we're being thorough besties:

• response_type — the type of this event, and in this case it's XCB_INPUT_KEY_RELEASE. yes you read that right, the manpage really says XCB_INPUT_KEY_RELEASE for the key press event. that's what it says, and we do not editorialize, we just report. 📋 this field is also hanging out in the xcb_generic_event_t, which is how you tell one event apart from another. super handy.
• sequence — the sequence number of the last request that the X11 server actually processed. like a little receipt number for your requests. 🧾
• extension — NOT YET DOCUMENTED. (the docs are being shy, we don't know her yet 🙈)
• length — NOT YET DOCUMENTED.
• event_type — NOT YET DOCUMENTED.
• deviceid — NOT YET DOCUMENTED.
• time — NOT YET DOCUMENTED.
• detail — NOT YET DOCUMENTED.
• root — NOT YET DOCUMENTED.
• event — NOT YET DOCUMENTED.
• child — NOT YET DOCUMENTED.
• full_sequence — NOT YET DOCUMENTED.
• root_x — NOT YET DOCUMENTED.
• root_y — NOT YET DOCUMENTED.
• event_x — NOT YET DOCUMENTED.
• event_y — NOT YET DOCUMENTED.
• buttons_len — NOT YET DOCUMENTED.
• valuators_len — NOT YET DOCUMENTED.
• sourceid — NOT YET DOCUMENTED.
• flags — NOT YET DOCUMENTED.
• mods — NOT YET DOCUMENTED.
• group — NOT YET DOCUMENTED.

lowkey a lot of "NOT YET DOCUMENTED" up in here 😭 that's genuinely all the original gives us though, so we are NOT inventing lore. if you need these, go read the source, bestie. 🔍

---

💀 DESCRIPTION 💀

...there is none. the DESCRIPTION section is empty. truly the "no thoughts, head empty" of manpage sections. we respect it. ✨

---

🌈 SEE ALSO 🌈

also empty bestie!! nothing to see, nothing to also. it's giving minimalism. 💅

---

👑 AUTHOR 👑

Generated from xinput.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org — they wanna hear from you, fr fr. 🫶

---

and that's the whole page, babe! this one came from X Version 11 / libxcb 1.17.0, so if you cite it or file a bug, that's the version tea you need. 💖✨🎀🦋🌸

go forth and handle those input events, you gorgeous little X11 gremlin. periodt. 💅💜