XCB_INPUT_SEND_EXTENSION_EVENT(3)

✨ xcb_input_send_extension_event ✨

ok so bestie, gather round, we're reading a libxcb manpage together 💖 this one lives in section 3 of the manual (the library-call section, iykyk) and it's called xcb_input_send_extension_event. yes it's a whole mouthful. no we're not skipping any of it. periodt.

---

🌸 NAME 🌸

xcb_input_send_extension_event — and honestly? that's it. the original page doesn't even give us a one-liner here, it just... says the name and vibes. so we're matching that energy exactly. no description in NAME, no cap.

---

🦋 SYNOPSIS 🦋

first you gotta pull in the header, obviously:

#include <xcb/xinput.h>

✨ Request function ✨

here's the actual function, character for character, don't you dare typo it:

xcb_void_cookie_t xcb_input_send_extension_event(xcb_connection_t *conn,
       xcb_window_t destination, uint8_t device_id, uint8_t propagate,
       uint16_t num_classes, uint8_t num_events, const
       xcb_input_event_for_send_t *events, const
       xcb_input_event_class_t *classes);

look at all those parameters. she's got range 💅

---

🎀 REQUEST ARGUMENTS 🎀

• conn — the XCB connection to X11. your lil hotline to the X server, bestie 🫶
• destination — TODO: NOT YET DOCUMENTED. yeah. the docs really just left us on read with this one 😭
• device_id — TODO: NOT YET DOCUMENTED. same situation, babe 🙈
• propagate — TODO: NOT YET DOCUMENTED. the mystery continues ✨
• num_classes — TODO: NOT YET DOCUMENTED. iconic of them to not write it down 💀
• num_events — TODO: NOT YET DOCUMENTED. not a single crumb of lore 🍓
• events — TODO: NOT YET DOCUMENTED. she's giving enigmatic main character energy 👑
• classes — TODO: NOT YET DOCUMENTED. and that's the whole list, all seven, nothing skipped 🌈

ngl the original manpage literally has TODO: NOT YET DOCUMENTED. on every single one of these. i'm not making it up and i'm not filling in the blanks — that would be inventing facts and we do NOT do that here 💖

---

🌟 DESCRIPTION 🌟

so here's the thing. the original DESCRIPTION section is... empty. completely. no prose, no explanation, nothing but the heading. i am not going to make something up for you because guessing at what a request does is how you end up with bug reports, and we are too cute for bug reports.

what i can tell you is what's actually written down elsewhere on this page, which is: the request arguments are listed above, the return value is a xcb_void_cookie_t, and the ERRORS section has a genuinely nice surprise for you. keep scrolling 📜

---

💅 RETURN VALUE 💅

it hands you back an xcb_void_cookie_t. errors (if any) have to be handled in the event loop — that's the rules, bestie.

and if you'd rather handle errors directly with xcb_request_check instead, use xcb_input_send_extension_event_checked. see xcb-requests(3) for the deets. go read it, it's good for you 🧚

---

🔥 ERRORS 🔥

This request does never generate any errors.

that's it. that's the whole section. she's flawless, she's never wrong, she has never once caused a problem in her life. periodt 💖✨

---

👑 SEE ALSO 👑

the original page's SEE ALSO section is empty, so... nothing to link you to here. a whole section with nothing in it. relatable tbh.

---

🍓 AUTHOR 🍓

Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. (yes, they want your emails. they're friendly like that 🫶)

---

okay bestie that's the whole page, every heading, every argument, every TODO, all of it accounted for 💖 no detail left behind, no options invented, we kept it 100.

this lil beauty comes from X Version 11, libxcb 1.17.0 — mwah, love that for us 💅✨