XCB_RANDR_GET_PROVIDER_PROPERTY_DATA(3)
π NAME
xcb_randr_get_provider_property β bestie, this is the XCB request that pulls a property off a RandR provider. That's it, that's the whole name. (Yeah, the title got chopped in the manpage header β the full thing is xcb_randr_get_provider_property, and it lives in section 3 of the manual, the library-call zone. π)
β¨ SYNOPSIS
Okay so first, you gotta let the compiler know you want in:
#include <xcb/randr.h>
πΈ Request function
xcb_randr_get_provider_property_cookie_t
xcb_randr_get_provider_property(xcb_connection_t *conn,
xcb_randr_provider_t provider, xcb_atom_t property,
xcb_atom_t type, uint32_t long_offset, uint32_t long_length,
uint8_t _delete, uint8_t pending);
π¦ Reply datastructure
typedef struct xcb_randr_get_provider_property_reply_t {
uint8_t response_type;
uint8_t format;
uint16_t sequence;
uint32_t length;
xcb_atom_t type;
uint32_t bytes_after;
uint32_t num_items;
uint8_t pad0[12];
} xcb_randr_get_provider_property_reply_t;
π Reply function
xcb_randr_get_provider_property_reply_t
*xcb_randr_get_provider_property_reply(xcb_connection_t *conn,
xcb_randr_get_provider_property_cookie_t cookie,
xcb_generic_error_t **e);
π§ Reply accessors
void *xcb_randr_get_provider_property_data(const
xcb_randr_get_provider_property_request_t *reply);
int xcb_randr_get_provider_property_data_length(const
xcb_randr_get_provider_property_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_provider_property_data_end(const
xcb_randr_get_provider_property_reply_t *reply);
π«Ά REQUEST ARGUMENTS
connβ your XCB connection to X11. The whole vibe conduit, the link to the server, the group chat. πproviderβ TODO: NOT YET DOCUMENTED. (Not me exposing the docs like this π the upstream authors left this one blank, bestie. No cap, I'm not gonna make something up.)propertyβ TODO: NOT YET DOCUMENTED. (Same situation, we stay honest. π)typeβ TODO: NOT YET DOCUMENTED. (Left blank upstream, fr fr.)long_offsetβ TODO: NOT YET DOCUMENTED. (Also blank. Iconic of them tbh.)long_lengthβ TODO: NOT YET DOCUMENTED. (Still blank, still not inventing anything. π)_deleteβ TODO: NOT YET DOCUMENTED. (Yep, blank. Notice the leading underscore, that's literally part of the name, don't drop it.)pendingβ TODO: NOT YET DOCUMENTED. (Blank. We move.)
Real talk: all those TODOs are straight from the source docs. Nothing is being hidden from you β it's just not written yet. π
π REPLY FIELDS
response_typeβ the type of this reply, which in this case isXCB_RANDR_GET_PROVIDER_PROPERTY. This field is also hanging out in thexcb_generic_reply_t, so you can use it to tell replies apart from each other. Very much the "which one of y'all texted me" field. β¨sequenceβ the sequence number of the last request processed by the X11 server. The receipt number, basically.lengthβ the length of the reply, in words. And a word here is 4 bytes, so do the math, babe. πΈformatβ TODO: NOT YET DOCUMENTED. (Blank upstream. We're not making it up.)typeβ TODO: NOT YET DOCUMENTED. (Also blank. Yeah.)bytes_afterβ TODO: NOT YET DOCUMENTED. (Blank.)num_itemsβ TODO: NOT YET DOCUMENTED. (Blank, bestie. That's the whole tea. π¦)
π DESCRIPTION
So this section is literally empty in the original. Nothing. A whole heading and zero words underneath it. It's giving "left on read." π
π₯ RETURN VALUE
It hands you back an xcb_randr_get_provider_property_cookie_t. That's the cookie, and no, you don't eat it β you trade it in later.
Errors have to be handled when you call the reply function xcb_randr_get_provider_property_reply.
But wait, there's a plot twist: if you'd rather handle errors in the event loop instead, use xcb_randr_get_provider_property_unchecked. And go read xcb-requests(3) for the details, because that page has the full lore. π
π ERRORS
This request does never generate any errors. Zero. None. Clean record, no drama, we love that for it. π
π SEE ALSO
(There's nothing listed here in the original. Just vibes and an empty section. Consider this your moment of silence. π)
π AUTHOR
Generated from randr.xml. If you want to send corrections or improvements, contact xcb@lists.freedesktop.org. They're the ones holding the pen β go tell them about those TODOs, bestie, they'd probably appreciate it. π«Ά
Okay that's the whole page!! Now go forth and query those provider properties. This page came to you from X Version 11, libxcb 1.17.0 β thanks for reading, mwah, slay, periodt. πβ¨ππ¦
π¦ 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