xcb_xkb_set_device_info(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

✨ xcb_xkb_set_device_info ✨

okay bestie, welcome to another XCB Requests baddie: xcb_xkb_set_device_info(3). it's a whole request function, it lives in the XKB corner of libxcb, and it is genuinely here to set device info. no cap. πŸ’–


🌸 NAME 🌸

xcb_xkb_set_device_info β€” and honestly? the upstream page left the description blank. like, empty. nothing. a lil dash and vibes. so that's what we're working with, bestie πŸ’€ (we still love her)


πŸŽ€ SYNOPSIS πŸŽ€

first things first, you gotta pull in the header:

#include <xcb/xkb.h>

✨ Request function ✨

xcb_void_cookie_t xcb_xkb_set_device_info(xcb_connection_t *conn,
       xcb_xkb_device_spec_t deviceSpec, uint8_t firstBtn,
       uint8_t nBtns, uint16_t change, uint16_t nDeviceLedFBs, const
       xcb_xkb_action_t *btnActions, const
       xcb_xkb_device_led_info_t *leds);

look at all those params. she's thorough. she's committed. periodt πŸ’…


πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11. your whole lil link to the X server, the main character of every request, as always πŸ’œ
  • deviceSpec β€” TODO: NOT YET DOCUMENTED. (the docs said "figure it out" and honestly same πŸ™ˆ)
  • firstBtn β€” TODO: NOT YET DOCUMENTED.
  • nBtns β€” TODO: NOT YET DOCUMENTED.
  • change β€” TODO: NOT YET DOCUMENTED.
  • nDeviceLedFBs β€” TODO: NOT YET DOCUMENTED.
  • btnActions β€” TODO: NOT YET DOCUMENTED.
  • leds β€” TODO: NOT YET DOCUMENTED.
bestie, real talk: every single one of these is literally marked TODO: NOT YET DOCUMENTED. in the original. i'm not hiding anything from you β€” that is the documentation. iconic in a cursed way 🫢

πŸ’… DESCRIPTION πŸ’…

...it's empty. that's it. that's the section. the original has a DESCRIPTION heading and then absolutely nothing underneath it, and i refuse to invent lore that isn't there. we respect the mystery 😭✨


🌈 RETURN VALUE 🌈

she hands you back an xcb_void_cookie_t. and because it's a void cookie, any errors (if any even show up) have to be handled over in the event loop β€” that's just how the void girls do it.

if you'd rather deal with errors directly using xcb_request_check, then you want xcb_xkb_set_device_info_checked instead. slay, there's a checked twin for exactly this πŸ’–

for the full tea, go read xcb-requests(3).


πŸ”₯ ERRORS πŸ”₯

this request does never generate any errors. not one. zero. a peaceful, unbothered queen πŸ‘‘


πŸ‘‘ SEE ALSO πŸ‘‘

(blank. nothing listed. just empty space where the cross-references would be. we love a minimalist moment πŸŽ€)


πŸ’œ AUTHOR πŸ’œ

generated from xkb.xml. if you spot something wrong or wanna send improvements, hit up xcb@lists.freedesktop.org β€” they're the ones who want your corrections and improvements, so don't be shy bestie 🫢


k that's the whole page, you absolutely ate this one. this lil rewrite is chillin' on X Version 11, running libxcb 1.17.0, and it's page xcb_xkb_set_device_info(3) β€” take care of her, mwah πŸ’…πŸ’–βœ¨