xcb_input_touch_begin_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_touch_begin_event_t β€” the XCB Events glow-up

okay so bestie, you've stumbled into the xcb_input_touch_begin_event_t page from the XCB Events corner of the universe. it's a struct. it's giving "touch began, and here's literally every scrap of info about it." let's get into it 🫢


✨ NAME ✨

xcb_input_touch_begin_event_t β€” that's the whole name, no subtitle, no little tagline, she's mysterious like that πŸ’…


🌸 SYNOPSIS 🌸

first things first, you gotta bring her in:

#include <xcb/xinput.h>

πŸŽ€ Event datastructure

this is the actual shape of her. copy it exactly, no freestyling:

typedef struct xcb_input_touch_begin_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_touch_begin_event_t;

πŸ”₯ EVENT FIELDS πŸ”₯

every single field, one by one, no skipping, no "eh you get the vibe." here we go πŸ‘‘

  • response_type β€” the type of this event, and in this case it's XCB_INPUT_TOUCH_END. yes bestie, the page really does say XCB_INPUT_TOUCH_END on the touch begin event page. iconic. anyway, this field also lives in the xcb_generic_event_t and it's how you tell your events apart from each other πŸ’«
  • sequence β€” the sequence number of the last request processed by the X11 server.
  • extension β€” NOT YET DOCUMENTED.
  • 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.
ngl, a lot of "NOT YET DOCUMENTED" going on up there. that's not me being lazy, that's literally what the page says. don't come for me, come for xinput.xml 😭

πŸ¦‹ DESCRIPTION πŸ¦‹

...and that's it. there is genuinely no description text on this page. the section exists, and it is empty. main character energy of a section that just shows up and says nothing. we respect her privacy πŸŽ€


πŸ‘€ SEE ALSO πŸ‘€

also empty. no cross-references, no friends, no "go look at this other thing." she's solo. a lone wolf. πŸ’€


🌈 AUTHOR 🌈

generated from xinput.xml. if you wanna send corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're literally waiting for your email, bestie 🫢


that's the whole page, no cap. and before you go β€” this was X Version 11, libxcb 1.17.0, page xcb_input_touch_begin_event_t(3). thanks for coming to my ted talk, mwah πŸ’–βœ¨