xcb_get_motion_events(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_get_motion_events(3) 💖

okay bestie, welcome to xcb_get_motion_events(3) — she's from the XCB Requests section of the manual, and she's here to get you them motion events. let's go 🦋

✨ NAME ✨

xcb_get_motion_events —

…and that's literally it, bestie. the description slot is empty. no cap. the manpage just leaves it hanging like a text left on read 💀

✨ SYNOPSIS ✨

first things first, you gotta pull in the header:

#include <xcb/xproto.h>

🌸 Request function 🌸

xcb_get_motion_events_cookie_t
       xcb_get_motion_events(xcb_connection_t *conn,
       xcb_window_t window, xcb_timestamp_t start,
       xcb_timestamp_t stop);

🌸 Reply datastructure 🌸

typedef struct xcb_get_motion_events_reply_t {
    uint8_t  response_type;
    uint8_t  pad0;
    uint16_t sequence;
    uint32_t length;
    uint32_t events_len;
    uint8_t  pad1[20];
} xcb_get_motion_events_reply_t;

🌸 Reply function 🌸

xcb_get_motion_events_reply_t
       *xcb_get_motion_events_reply(xcb_connection_t *conn,
       xcb_get_motion_events_cookie_t cookie, xcb_generic_error_t **e);

🌸 Reply accessors 🌸

xcb_timecoord_t *xcb_get_motion_events_events(const
       xcb_get_motion_events_request_t *reply);

int xcb_get_motion_events_events_length(const
       xcb_get_motion_events_reply_t *reply);

xcb_timecoord_iterator_t xcb_get_motion_events_events_iterator(const
       xcb_get_motion_events_reply_t *reply);

like, three lil helpers to get at your events, count them, and iterate them. slay 💅

✨ REQUEST ARGUMENTS ✨

  • conn — your XCB connection to X11. the whole vibe check with the server happens through her 🫶
  • window — TODO: NOT YET DOCUMENTED. yeah bestie, the docs ghosted us on this one 😭
  • start — TODO: NOT YET DOCUMENTED. also ghosted 🙈
  • stop — TODO: NOT YET DOCUMENTED. ghosted too 💀

✨ REPLY FIELDS ✨

  • response_type — the type of this reply, which in this case is XCB_GET_MOTION_EVENTS. this field is also chillin' inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other. iconic behavior honestly ⭐
  • sequence — the sequence number of the last request that got processed by the X11 server. it's giving receipt energy 🧾
  • length — the length of the reply, in words. and reminder: a word is 4 bytes, periodt 📏
  • events_len — TODO: NOT YET DOCUMENTED. yeah… nothing. the void. the silence 🌈

✨ DESCRIPTION ✨

bestie. there is literally nothing here. the DESCRIPTION section is empty. it's giving blank notes app page. i cannot make up lore that isn't in the source, so i'm just gonna hold your hand and we move on 💜

✨ RETURN VALUE ✨

she hands you back an xcb_get_motion_events_cookie_t 🍪 and listen — errors have to be handled when you call the reply function xcb_get_motion_events_reply.

but if you'd rather handle your errors in the event loop instead, use xcb_get_motion_events_unchecked. see xcb-requests(3) for the details, iykyk ✨

✨ ERRORS ✨

this request does never generate any errors. not one. zero. clean sheet. she's an angel, no drama, no red flags 🌸👑

✨ SEE ALSO ✨

nothing here either bestie. empty. a whole section of absolutely nothing. we respect her privacy 🎀

✨ AUTHOR ✨

Generated from xproto.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. go off, xml file 👑

and that's the whole page, bestie!! ty for reading, mwah 💖

this has been X Version 11, libxcb 1.17.0, page xcb_get_motion_events(3) — see you in the group chat 🦋✨

📦 where this page comes from