XCB_INPUT_GET_FEEDBACK_CONTROL_UNCHECKED(3)
πΈ xcb_input_get_feedback_control(3) πΈ
okay bestie, welcome to the manual page for xcb_input_get_feedback_control, part of the XCB Requests fam (that's the xcb_input_get_feedback_control(3) manual, if you're keeping track, and you should be π
).
This is the lil request that asks the X server "hey, what's the feedback control situation for this device" and hands you back a cookie you gotta cash in later. Very demure. Very mindful. Let's get into it. π
β¨ NAME β¨
xcb_input_get_feedback_control β the name is literally right there, and the original page left the description blank, so we're just vibing with the function name itself π¦
β¨ SYNOPSIS β¨
First things first, you gotta let the preprocessor know what's up:
#include <xcb/xinput.h>
π Request function π
xcb_input_get_feedback_control_cookie_t
xcb_input_get_feedback_control(xcb_connection_t *conn,
uint8_t device_id);
π Reply datastructure π
this is the struct that comes back at you, no cap:
typedef struct xcb_input_get_feedback_control_reply_t {
uint8_t response_type;
uint8_t xi_reply_type;
uint16_t sequence;
uint32_t length;
uint16_t num_feedbacks;
uint8_t pad0[22];
} xcb_input_get_feedback_control_reply_t;
π Reply function π
this is the one that actually fetches your reply, so like, don't forget to call it:
xcb_input_get_feedback_control_reply_t
*xcb_input_get_feedback_control_reply(xcb_connection_t *conn,
xcb_input_get_feedback_control_cookie_t cookie,
xcb_generic_error_t **e);
π Reply accessors π
the little helpers that go digging inside the reply for you, iconic behavior:
int xcb_input_get_feedback_control_feedbacks_length(const
xcb_input_get_feedback_control_reply_t *reply);
xcb_input_feedback_state_iterator_t
xcb_input_get_feedback_control_feedbacks_iterator(const
xcb_input_get_feedback_control_reply_t *reply);
β¨ REQUEST ARGUMENTS β¨
connβ yourXCBconnection to X11. the whole lifeline, the group chat server, everything flows through here π«Άdevice_idβ TODO: NOT YET DOCUMENTED. yeah bestie, the original page literally says that. not my fault, i'm just the messenger π
β¨ REPLY FIELDS β¨
response_typeβ the type of this reply, and in this case it'sXCB_INPUT_GET_FEEDBACK_CONTROL. this field is also chillin' insidexcb_generic_reply_t, so you can use it to tell your replies apart from each other. very "which one of y'all texted me" energy πsequenceβ the sequence number of the last request the X11 server processed. your lil timestamp of "yeah we got here" βlengthβ how long the reply is, measured in words. and heads up, a word is 4 bytes. that's the unit. don't come at me with bytes, that's not the vibe here πxi_reply_typeβ TODO: NOT YET DOCUMENTED. yep. blank. the original said so πnum_feedbacksβ TODO: NOT YET DOCUMENTED. also blank. also not my fault. also we move π
β¨ DESCRIPTION β¨
so the DESCRIPTION section on the original page isβ¦ completely empty. nothing. a void. the silence is loud. i'm not gonna make up lore about what this request does because that would be inventing technical claims and we don't do that here, bestie β we keep the facts exactly as they were handed to us. the section is empty, and it stays empty, and that's just how the original rolled. π¦β¨
β¨ RETURN VALUE β¨
it returns an xcb_input_get_feedback_control_cookie_t. that's your cookie πͺ β a lil promise of a reply.
errors? you handle those when you call the reply function, xcb_input_get_feedback_control_reply.
and if you'd rather deal with errors inside your event loop instead of right here, use xcb_input_get_feedback_control_unchecked. peek xcb-requests(3) for the deets on how that whole unchecked situation works π
β¨ ERRORS β¨
this request does never generate any errors. like, ever. zero. none. it's the chillest request in the whole building, no drama, no nothing. π
β¨ SEE ALSO β¨
nothing listed here in the original, bestie. an empty section. we respect it. we leave it. π
β¨ AUTHOR β¨
generated from xinput.xml. if you've got corrections or improvements, hit up xcb@lists.freedesktop.org β they're the ones who actually want to hear it, not me, i'm just the messenger with a keyboard and a dream π
and that's a wrap, queen π this page came to you from X Version 11, libxcb 1.17.0. slay, go forth, cash in that cookie, and don't forget to free your replies πβ¨π¦πΈπ
π¦ where this page comes from
- alpine 3.22: libxcb-doc 1.17.0-r0 Β· MIT
- alpine 3.23: libxcb-doc 1.17.0-r1 Β· MIT
- alpine 3.24: libxcb-doc 1.17.0-r2 Β· MIT
- arch rolling: libxcb 1.17.0-1 Β· X11
- centos-stream 10: libxcb-devel 1.17.0-3.el10 Β· X11
- debian trixie: libxcb-doc 1.17.0-2
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 43: libxcb-devel 1.17.0-6.fc43 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- fedora 44: libxcb-devel 1.17.0-7.fc44 Β· X11
- nixpkgs unstable: libxcb 1.17.0
- opensuse-leap 16.0: libxcb-devel-doc 1.17.0-160000.2.2 Β· MIT
- ubuntu questing: libxcb-doc 1.17.0-2build1
- ubuntu resolute: libxcb-doc 1.17.0-2ubuntu1
- ubuntu stonking: libxcb-doc 1.17.0-2ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms