XCB_INPUT_GET_EXTENSION_VERSION_REPLY(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

πŸ’– NAME πŸ’–

xcb_input_get_extension_version β€” bestie, this is the X Input extension version asker, and honestly? The docs left it blank for us. We ball anyway. πŸŽ€


✨ SYNOPSIS ✨

Header first, always:

#include <xcb/xinput.h>

πŸ¦‹ Request function

xcb_input_get_extension_version_cookie_t
       xcb_input_get_extension_version(xcb_connection_t *conn,
       uint16_t name_len, const char *name);

🫢 Reply datastructure

typedef struct xcb_input_get_extension_version_reply_t {
           uint8_t  response_type;
           uint8_t  xi_reply_type;
           uint16_t sequence;
           uint32_t length;
           uint16_t server_major;
           uint16_t server_minor;
           uint8_t  present;
           uint8_t  pad0[19];
       } xcb_input_get_extension_version_reply_t;

🌸 Reply function

xcb_input_get_extension_version_reply_t
       *xcb_input_get_extension_version_reply(xcb_connection_t *conn,
       xcb_input_get_extension_version_cookie_t cookie,
       xcb_generic_error_t **e);

πŸ’… REQUEST ARGUMENTS

  • conn β€” the XCB connection to X11. Your little phone line to the server, no cap. πŸ“ž
  • name_len β€” TODO: NOT YET DOCUMENTED. Yeah bestie, they really just left us on read for this one. 😭
  • name β€” TODO: NOT YET DOCUMENTED. Same energy. The mystery stays mysterious. πŸ•΅οΈβ™€οΈ

πŸ‘‘ REPLY FIELDS

  • response_type β€” the type of this reply, and in this case it's XCB_INPUT_GET_EXTENSION_VERSION. This field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other like, "wait, which one are you?" and it just tells you. Iconic behaviour, honestly. ✨
  • sequence β€” the sequence number of the last request the X11 server actually processed. Basically the server's "seen it, handled it πŸ’…" receipt.
  • length β€” how long the reply is, measured in words. And a word here is 4 bytes, just so we're clear. 🧚
  • xi_reply_type β€” TODO: NOT YET DOCUMENTED. Ugh.
  • server_major β€” TODO: NOT YET DOCUMENTED. The lore is missing, bestie.
  • server_minor β€” TODO: NOT YET DOCUMENTED. Also missing.
  • present β€” TODO: NOT YET DOCUMENTED. Genuinely nothing. Not a crumb. πŸ“

🌈 DESCRIPTION

(The original page has literally nothing here. A blank canvas. Main character silence. I'm not gonna invent facts to fill it, because that's not the vibe β€” the vibe is accuracy.)


πŸ”₯ RETURN VALUE

You get back an xcb_input_get_extension_version_cookie_t. πŸͺ A cookie! And cookies mean the errors don't show up here β€” you have to handle them when you call the reply function, xcb_input_get_extension_version_reply.

If you'd rather handle your errors in the event loop instead, then use xcb_input_get_extension_version_unchecked. And for the whole lore on how this cookie/reply dance works, go read xcb-requests(3). Periodt. πŸ’–


πŸ’€ ERRORS

This request does never generate any errors. Not one. Zero. Clean sheet, flawless, no drama. Slay. ✨


πŸ’œ SEE ALSO

(Nothing listed on this page β€” go touch some other manpages, bestie.)


πŸŽ€ AUTHOR

Generated from xinput.xml. If you've got corrections or improvements, hit up xcb@lists.freedesktop.org β€” they're literally asking, so don't be shy. πŸ“¬


And that's the whole page, bestie! This was xcb_input_get_extension_version(3) from the XCB Requests manual, coming to you courtesy of X Version 11, libxcb 1.17.0. Stay hydrated, stay linked, and remember: read the reply, handle the cookie. πŸ’…πŸ¦‹