XCB_INPUT_RAW_BUTTON_PRESS_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_raw_button_press_event_t ✨

okay bestie, welcome to the xcb_input_raw_..._press_event_t(3) page from the XCB Events manual πŸ’… this is a raw button press event, it's giving "input internals" energy, and we're gonna walk through it together 🫢


🌸 NAME 🌸

xcb_input_raw_button_press_event_t β€” literally just the name, no extra lore, that's the whole section, periodt πŸ’–


✨ SYNOPSIS ✨

first things first, you gotta bring in the header:

#include <xcb/xinput.h>

πŸŽ€ Event datastructure πŸŽ€

here's the struct, and yes, every field matters, don't touch anything:

typedef struct xcb_input_raw_button_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_input_device_id_t sourceid;
    uint16_t              valuators_len;
    uint32_t              flags;
    uint8_t               pad0[4];
    uint32_t              full_sequence;
} xcb_input_raw_button_press_event_t;

πŸ¦‹ EVENT FIELDS πŸ¦‹

okay so let's go field by field, no skipping, we're thorough in this house πŸ‘‘

  • response_type β€” the type of this event, and in this case it's XCB_INPUT_RAW_MOTION. yes, we know, that's what it says, we're just reporting it, don't shoot the messenger 😭 this field also lives in the xcb_generic_event_t, so you can use it to tell your events apart from each other, very slay of it.
  • sequence β€” the sequence number of the last request processed by the X11 server. tracking numbers but make it X11 πŸ’…
  • extension β€” NOT YET DOCUMENTED. yeah bestie, it's giving mystery. πŸ™ˆ
  • length β€” NOT YET DOCUMENTED. also a mystery πŸŽ€
  • event_type β€” NOT YET DOCUMENTED. mystery #3 🌸
  • deviceid β€” NOT YET DOCUMENTED. mystery #4, the mystery continues πŸ¦‹
  • time β€” NOT YET DOCUMENTED. mystery #5, we're on a roll πŸ’œ
  • detail β€” NOT YET DOCUMENTED. mystery #6, no cap ✨
  • sourceid β€” NOT YET DOCUMENTED. mystery #7, the plot thickens πŸ’«
  • valuators_len β€” NOT YET DOCUMENTED. mystery #8 πŸŽ€
  • flags β€” NOT YET DOCUMENTED. mystery #9, so many little question marks πŸ”₯
  • full_sequence β€” NOT YET DOCUMENTED. mystery #10, and that's a wrap on the mystery tour 😌

πŸ’– DESCRIPTION πŸ’–

so... this section is just. empty. bestie it is literally blank. nothing to describe, the description section said "not my job today" and walked out 😭 we respect the boundaries tho πŸ’…


🌈 SEE ALSO 🌈

also empty!! iconic honestly. nothing to see here, move along, nothing to see 🌸


πŸ‘‘ AUTHOR πŸ‘‘

this page was generated from xinput.xml. and if you spot something wrong or wanna send improvements, hit up xcb@lists.freedesktop.org β€” they're the ones to contact for corrections and improvements, fr fr πŸ’Œ


and that's the whole page bestie!! slay πŸŽ€ this was brought to you by X Version 11 and libxcb 1.17 β€” go forth and handle your raw button press events, you've got this πŸ’–βœ¨πŸ¦‹