xcb_test_compare_cursor(3)
β¨ xcb_test_compare_cursor β¨
okay bestie, pull up a chair because we're looking at a page from the XCB Requests chapter of the manual, and this one is literally called xcb_test_compare_cursor. it's from the XTEST family, it lives in libxcb, and it does exactly one little job: ask the X server "hey, is this cursor the one on this window?" π
πΈ NAME πΈ
xcb_test_compare_cursor β
fr fr, that's it. the original page leaves this one blank after the dash, so we're not gonna invent a description. mysterious queen behavior. π
π¦ SYNOPSIS π¦
First things first, you gotta bring in the header:
#include <xcb/xtest.h>
Request function π
xcb_test_compare_cursor_cookie_t
xcb_test_compare_cursor(xcb_connection_t *conn,
xcb_window_t window, xcb_cursor_t cursor);
Reply datastructure π§
typedef struct xcb_test_compare_cursor_reply_t {
uint8_t response_type;
uint8_t same;
uint16_t sequence;
uint32_t length;
} xcb_test_compare_cursor_reply_t;
Reply function π
xcb_test_compare_cursor_reply_t
*xcb_test_compare_cursor_reply(xcb_connection_t *conn,
xcb_test_compare_cursor_cookie_t cookie,
xcb_generic_error_t **e);
π REQUEST ARGUMENTS π
connβ the XCB connection to X11. your lil hotline to the server, no cap.windowβ TODO: NOT YET DOCUMENTED. yeah bestie, the docs said "we'll get to it" and then never did. πcursorβ TODO: NOT YET DOCUMENTED. same energy. iconic of them, honestly.
π REPLY FIELDS π
response_typeβ what kind of reply this is. in this case it'sXCB_TEST_COMPARE_CURSOR. this field is also hanging out in thexcb_generic_reply_t, so you can use it to tell your replies apart from each other. very "which one of you is which" of it. π₯sequenceβ the sequence number of the last request the X11 server processed.lengthβ how long the reply is, measured in words. and yes, a word here is 4 bytes. periodt.sameβ TODO: NOT YET DOCUMENTED. the original really just left us on read for this one. π
π DESCRIPTION π
genuinely nothing here. the original page has an empty DESCRIPTION section, so there is no prose for me to translate. we respect the silence. π«Ά
β RETURN VALUE β
You get back an xcb_test_compare_cursor_cookie_t. that's your lil claim ticket. ποΈ
Errors? those have to be handled when you call the reply function, xcb_test_compare_cursor_reply.
But if you'd rather handle errors in the event loop instead, use xcb_test_compare_cursor_unchecked. see xcb-requests(3) for the details, iykyk.
π ERRORS π
This request never generates any errors. not one. zero. clean slate. we love a low-drama request. β¨
πΈ SEE ALSO πΈ
empty in the original! no cross-references listed here at all. shocking, I know. π
π AUTHOR π
Generated from xtest.xml. For corrections and improvements, contact xcb@lists.freedesktop.org.
and that's the whole page, bestie! π¦ this one came from X Version 11, and it's part of libxcb 1.17.0 β so if you're running that, you're running this exact vibe. mwah, go forth and compare those cursors. π π
π¦ 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