XCB_INPUT_SET_DEVICE_VALUATORS(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_set_device_valuators — bestie, the NAME section literally left this blank, so consider this your vibe check: it's the XCB request that sets a device's valuators 💅

🌸 SYNOPSIS 🌸

okay so first, include the header, no cap:

#include <xcb/xinput.h>

🎀 Request function

xcb_input_set_device_valuators_cookie_t
       xcb_input_set_device_valuators(xcb_connection_t *conn,
       uint8_t device_id, uint8_t first_valuator, uint8_t num_valuators,
       const int32_t *valuators);

🦋 Reply datastructure

typedef struct xcb_input_set_device_valuators_reply_t {
    uint8_t  response_type;
    uint8_t  xi_reply_type;
    uint16_t sequence;
    uint32_t length;
    uint8_t  status;
    uint8_t  pad0[23];
} xcb_input_set_device_valuators_reply_t;

💖 Reply function

xcb_input_set_device_valuators_reply_t
       *xcb_input_set_device_valuators_reply(xcb_connection_t *conn,
       xcb_input_set_device_valuators_cookie_t cookie,
       xcb_generic_error_t **e);

👑 REQUEST ARGUMENTS 👑

  • conn — the XCB connection to X11. your lil hotline to the server, periodt 💫
  • device_id — TODO: NOT YET DOCUMENTED. yeah bestie, they really just left us on read 🙈
  • first_valuator — TODO: NOT YET DOCUMENTED. same energy 😭
  • num_valuators — TODO: NOT YET DOCUMENTED. the docs said "not me being mysterious" 💀
  • valuators — TODO: NOT YET DOCUMENTED. iconic of them to keep us guessing fr fr

🌈 REPLY FIELDS 🌈

  • response_type — the type of this reply, and in this case it's XCB_INPUT_SET_DEVICE_VALUATORS. this field also lives in the xcb_generic_reply_t, so you can use it to tell your replies apart from each other 🕵️♀️
  • sequence — the sequence number of the last request processed by the X11 server. lowkey the receipts of the whole convo 🧾
  • length — the length of the reply, in words. and yes bestie, a word is 4 bytes ⭐
  • xi_reply_type — TODO: NOT YET DOCUMENTED. a mystery, a legend, a myth 🦄
  • status — TODO: NOT YET DOCUMENTED. we simply do not know and that's the tea ☕

💅 DESCRIPTION 💅

it's giving… absolutely nothing. the DESCRIPTION section is empty, no cap. the whole page is out here with main character energy and zero explanation 😭

🫶 RETURN VALUE 🫶

It returns an xcb_input_set_device_valuators_cookie_t. Errors have to be handled when you call the reply function xcb_input_set_device_valuators_reply.

If you'd rather handle errors in the event loop instead, use xcb_input_set_device_valuators_unchecked. See xcb-requests(3) for details ✨

💀 ERRORS 💀

This request does never generate any errors. like, not a single one. flawless behaviour, we love to see it 👑

🔥 SEE ALSO 🔥

empty. the SEE ALSO section has no references for us. bestie we are on our own out here 🧚

🌸 AUTHOR 🌸

Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

heads up bestie: device_id, first_valuator, num_valuators, valuators, xi_reply_type and status are all marked TODO: NOT YET DOCUMENTED in the original — that's not me being lazy, that's literally what it says 🙈

and that's the whole page, bestie 🎀 this came to you from X Version 11, libxcb 1.17.0 — stay iconic, read your manpages, and hydrate 💖✨🦋

📦 where this page comes from