XCB_INPUT_CHANGE_POINTER_DEVICE(3)

💖 xcb_input_change_pointer_device — bestie edition 💖

okay so. this is a page from XCB Requests, section 3 of the manual, and it's literally called xcb_input_change_pointer_device. that's the whole name, no subtitle, no vibes attached. the NAME section is just sitting there empty like a group chat with no messages. 🫶

---

✨ SYNOPSIS ✨

first, you gotta pull in the header:

#include <xcb/xinput.h>

🎀 Request function

xcb_input_change_pointer_device_cookie_t
       xcb_input_change_pointer_device(xcb_connection_t *conn,
       uint8_t x_axis, uint8_t y_axis, uint8_t device_id);

🎀 Reply datastructure

typedef struct xcb_input_change_pointer_device_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_change_pointer_device_reply_t;

🎀 Reply function

xcb_input_change_pointer_device_reply_t
       *xcb_input_change_pointer_device_reply(xcb_connection_t *conn,
       xcb_input_change_pointer_device_cookie_t cookie,
       xcb_generic_error_t **e);

---

🌸 REQUEST ARGUMENTS 🌸

• conn — the XCB connection to X11. your whole link to the server, the main character fr.
• x_axis — TODO: NOT YET DOCUMENTED. 😭 yeah bestie they just… didn't write it.
• y_axis — TODO: NOT YET DOCUMENTED. also a mystery. 💀
• device_id — TODO: NOT YET DOCUMENTED. same energy, no lore.

---

🦋 REPLY FIELDS 🦋

• response_type — the type of this reply, in this case XCB_INPUT_CHANGE_POINTER_DEVICE. this field also lives in the xcb_generic_reply_t, and it's literally how you tell replies apart from each other. it's giving name tag at a party. 👑
• sequence — the sequence number of the last request processed by the X11 server. so you know where you are in the timeline. ⭐
• length — the length of the reply, in words. and a word is 4 bytes, periodt.
• xi_reply_type — TODO: NOT YET DOCUMENTED. 🙈
• status — TODO: NOT YET DOCUMENTED. also blank, no cap.

---

💜 DESCRIPTION 💜

this section is empty in the original. nothing. void. a vibe check that returned no results. 😭

---

🌈 RETURN VALUE 🌈

you get back an xcb_input_change_pointer_device_cookie_t. cute little cookie. 🍓

errors? you gotta handle those when you call the reply function xcb_input_change_pointer_device_reply.

but listen — if you'd rather deal with errors in the event loop instead, use xcb_input_change_pointer_device_unchecked. see xcb-requests(3) for the details, iykyk.

---

💅 ERRORS 💅

this request does never generate any errors. iconic. flawless. zero drama. ✨

---

🧚 SEE ALSO 🧚

empty. nothing linked. just vibes. 🌸

---

💖 AUTHOR 💖

Generated from xinput.xml. contact xcb@lists.freedesktop.org for corrections and improvements. they're literally asking for your feedback bestie, don't leave them on read. 🫶

---

and that's the whole page!! brought to you by X Version 11, libxcb 1.17.0 — slay, go change that pointer device, and remember: the TODO sections aren't your fault, you're doing amazing. mwah 💋✨🎀