xcb_xkb_per_client_flags(3)

💖 xcb_xkb_per_client_flags(3) 💖

okay so bestie, welcome to the XCB Requests corner of the manual, where we're talking about xcb_xkb_per_client_flags(3) — yes the whole page is named after this one request, main character energy fr fr. Pull up a chair, grab a strawberry 🍓, and let's get into it.

---

✨ NAME ✨

xcb_xkb_per_client_flags —

lowkey the description here is just... empty? like the dash is there and then nothing. we move.

---

🌸 SYNOPSIS 🌸

First up, the include, because you literally cannot do anything without it:

#include <xcb/xkb.h>

🎀 Request function 🎀

xcb_xkb_per_client_flags_cookie_t
       xcb_xkb_per_client_flags(xcb_connection_t *conn,
       xcb_xkb_device_spec_t deviceSpec, uint32_t change,
       uint32_t value, uint32_t ctrlsToChange, uint32_t autoCtrls,
       uint32_t autoCtrlsValues);

🦋 Reply datastructure 🦋

this is the struct the server hands back, no cap:

typedef struct xcb_xkb_per_client_flags_reply_t {
    uint8_t  response_type;
    uint8_t  deviceID;
    uint16_t sequence;
    uint32_t length;
    uint32_t supported;
    uint32_t value;
    uint32_t autoCtrls;
    uint32_t autoCtrlsValues;
    uint8_t  pad0[8];
} xcb_xkb_per_client_flags_reply_t;

🫶 Reply function 🫶

and here's how you actually collect that struct:

xcb_xkb_per_client_flags_reply_t
       *xcb_xkb_per_client_flags_reply(xcb_connection_t *conn,
       xcb_xkb_per_client_flags_cookie_t cookie,
       xcb_generic_error_t **e);

---

🔥 REQUEST ARGUMENTS 🔥

• conn — the XCB connection to X11. your lil phone line to the server basically 💅
• deviceSpec — TODO: NOT YET DOCUMENTED. (yeah bestie, the docs just ghosted us here 😭)
• change — TODO: NOT YET DOCUMENTED.
• value — TODO: NOT YET DOCUMENTED.
• ctrlsToChange — TODO: NOT YET DOCUMENTED.
• autoCtrls — TODO: NOT YET DOCUMENTED.
• autoCtrlsValues — TODO: NOT YET DOCUMENTED.

---

🌈 REPLY FIELDS 🌈

• response_type — the type of this reply, and in this case it's XCB_XKB_PER_CLIENT_FLAGS. this field is also chillin' inside xcb_generic_reply_t, so you can use it to tell your replies apart from each other. very "which one of y'all is which" energy 👑
• sequence — the sequence number of the last request processed by the X11 server.
• length — the length of the reply, in words (and a word is 4 bytes, for the record).
• deviceID — TODO: NOT YET DOCUMENTED.
• supported — TODO: NOT YET DOCUMENTED.
• value — TODO: NOT YET DOCUMENTED.
• autoCtrls — TODO: NOT YET DOCUMENTED.
• autoCtrlsValues — TODO: NOT YET DOCUMENTED.

---

💜 DESCRIPTION 💜

so... the DESCRIPTION section is literally empty. like, nothing. not a single word. it's giving "the author left the group chat" 🙈 we're not gonna pretend there's more here than there is — the page just doesn't say.

---

⭐ RETURN VALUE ⭐

It returns an xcb_xkb_per_client_flags_cookie_t. Errors have to be handled when calling the reply function xcb_xkb_per_client_flags_reply.

If you want to handle errors in the event loop instead, use xcb_xkb_per_client_flags_unchecked. See xcb-requests(3) for details. yes bestie, that's a whole other manpage, go read it 🧚

---

💀 ERRORS 💀

This request does never generate any errors. not a single one. flawless behavior, honestly. periodt. 💅

---

🌟 SEE ALSO 🌟

...nothing here either bestie, the section is just vibes and emptiness 🦋

---

🎀 AUTHOR 🎀

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

ngl if you find something wrong, that's the email. they literally asked. don't be shy 🫶

---

okay that's the whole page!! and a lil sign-off for you: this beauty comes from X Version 11, libxcb 1.17.0, so if you're out here citing it, that's the version and source right there. slay, go forth, and may your replies never error ✨💖