xcb_xfixes_region_extents(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_xfixes_region_extents πŸ’–

okay bestie, so this one lives in the xcb family β€” specifically the XFixes extension β€” and it's a request function, meaning you're sending a request to the X server and getting a cookie back. The manpage is, and I say this with love, extremely sparse. Like, it's giving "we wrote the synopsis and then went to get boba." But we're gonna cover every crumb it gives us. πŸ“


✨ NAME ✨

xcb_xfixes_region_extents β€” and that's it. The description field is literally blank in the original, so I'm not gonna make one up for you. (iykyk)


🌸 SYNOPSIS 🌸

First, you gotta pull in the header:

#include <xcb/xfixes.h>

πŸŽ€ Request function πŸŽ€

xcb_void_cookie_t xcb_xfixes_region_extents(xcb_connection_t *conn,
       xcb_xfixes_region_t source, xcb_xfixes_region_t destination);

See that xcb_void_cookie_t return type? Yeah β€” it hands you back a cookie and no data. You deal with any errors later, in the event loop. More on that below. πŸ’…


πŸ¦‹ REQUEST ARGUMENTS πŸ¦‹

  • conn β€” the XCB connection to X11. Your link to the server, your main character, the whole vibe. πŸ”₯
  • source β€” TODO: NOT YET DOCUMENTED. yeah. that's the actual text. the docs simply did not show up. πŸ™ˆ
  • destination β€” also TODO: NOT YET DOCUMENTED. same energy. bestie, the documentation for these two is not serving. I refuse to invent behaviour that isn't in the page, so this is genuinely all we get. 😭
Real talk: if you need to know what source and destination actually do here, the manpage is not gonna tell you. That's a "go read the source / the XML" situation, fr fr.

πŸ’œ DESCRIPTION πŸ’œ

So... this section is empty in the original. Completely. Nothing. Not a single word. 🫢

I'm not gonna fill it with guesses, because guessing at X protocol behaviour is how you end up debugging at 3am. The section exists, it's just got nothing in it. Iconic in a "the audacity" kind of way. ✨


⭐ RETURN VALUE ⭐

You get an xcb_void_cookie_t back. Errors β€” if there are any β€” have to be handled in the event loop. That's the deal.

If you'd rather check for errors directly, right there, no event loop involved, use:

xcb_xfixes_region_extents_checked

instead. That's the checked variant. For all the deets on how that works, go see xcb-requests(3). πŸ‘‘


🌈 ERRORS 🌈

This request never generates any errors. Clean. No drama. No error codes to catch. We love a low-maintenance request. πŸ’š


🌸 SEE ALSO 🌸

Nothing listed here in the original β€” the section is empty. So there's nothing to send you off to. No links, no friends, just vibes. πŸ¦‹


πŸ’– AUTHOR πŸ’–

Generated from xfixes.xml. If you spot something wrong or wanna make it better, contact xcb@lists.freedesktop.org for corrections and improvements. They're the ones to @ basically. πŸ“§


And that's the whole page, bestie. Short, sweet, and 90% TODO. Not my fault, I'm just the messenger. πŸ˜­πŸ’…

X Version 11 Β· libxcb 1.17.0 Β· xcb_xfixes_region_extents(3) β€” mwah, take care of her, she's doing her best πŸŽ€βœ¨πŸ’œ