xcb_glx_chang...le_attributes(3)
β¨ NAME β¨
xcb_glx_change_drawable_attributes β bestie, that's it, that's the whole name. No little tagline, no explanation, the NAME section literally just drops the function name and dips π
(and yeah, the header truncates it to xcb_glx_chang...le_attributes(3), which is giving "we ran out of room at the party" energy).
This one lives in the XCB Requests manual, section 3, so it's a C library situation, not a command you type into your shell. π«Ά
πΈ SYNOPSIS πΈ
First things first, you gotta pull in the header:
#include <xcb/glx.h>
Request function
xcb_void_cookie_t
xcb_glx_change_drawable_attributes(xcb_connection_t *conn,
xcb_glx_drawable_t drawable, uint32_t num_attribs, const
uint32_t *attribs);
Look at that signature, it's iconic honestly. π₯
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. Your little red string to the X server, no cap. π§΅drawableβTODO: NOT YET DOCUMENTED.Yeah. The docs said "not yet" and then justβ¦ never came back. πnum_attribsβTODO: NOT YET DOCUMENTED.Same vibe, same void. πattribsβTODO: NOT YET DOCUMENTED.Three for three, the documentation is not beating the allegations. π
Not me pointing out that the entire argument list is unofficially "figure it out bestie" β I'm just the messenger, the TODOs are canon.
π DESCRIPTION π
Soβ¦ there is no description. Like, the section exists, it's labeled DESCRIPTION, and then it's just vibes and silence. π¦ The TODO: NOT YET DOCUMENTED. energy from the arguments carried all the way down here. Respect the commitment, honestly.
β RETURN VALUE β
It hands you back an xcb_void_cookie_t. And here's the tea: if errors happen, you do not get them handed to you directly β you have to handle them in the event loop. That's the deal. π
If you'd rather deal with errors immediately and directly with xcb_request_check instead, then use xcb_glx_change_drawable_attributes_checked β the _checked twin, she's the one who tells you things. β¨ And if you want the full rundown on how any of this request/cookie business works, go read xcb-requests(3). π
π ERRORS π
This request does never generate any errors. Periodt. Not a single one. Error-free queen behavior, we love to see it. π
π SEE ALSO π
Nothing. Empty. A whole section, zero references. It's giving "we had a slot open and filled it with air". π
π« AUTHOR π«
Generated from glx.xml. If you spot something wrong and wanna get it corrected or improved, hit up xcb@lists.freedesktop.org β they're the ones who can fix it up. π¬
That's the whole page bestie, you're officially fluent in xcb_glx_change_drawable_attributes(3). π«Ά This lil writeup shipped with libxcb 1.17.0 under X Version 11, so if your version number's different, don't come for me, come for the changelog. ππβ¨
π¦ 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