xcb_xv_get_still(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_xv_get_still β€” the manual page, bestie edition πŸ¦‹

okay so real talk, this is xcb_xv_get_still from the XCB Requests family of man pages, and she's a lil mysterious but we love her anyway. Let's get into it πŸ’…


✨ NAME ✨

xcb_xv_get_still β€” literally that's it, that's the name. The original didn't give us a description here, so I'm not about to make one up. No cap. πŸ™ˆ


🌸 SYNOPSIS 🌸

First things first, you gotta pull in the header:

#include <xcb/xv.h>

πŸŽ€ Request function

xcb_void_cookie_t xcb_xv_get_still(xcb_connection_t *conn,
       xcb_xv_port_t port, xcb_drawable_t drawable, xcb_gcontext_t gc,
       int16_t vid_x, int16_t vid_y, uint16_t vid_w, uint16_t vid_h,
       int16_t drw_x, int16_t drw_y, uint16_t drw_w, uint16_t drw_h);

Look at that signature. Twelve arguments. She's high maintenance and honestly? iconic. πŸ‘‘


πŸ’– REQUEST ARGUMENTS πŸ’–

Every single one of these is marked TODO: NOT YET DOCUMENTED. in the original, so I'm passing that energy straight through to you, no editorialising, no vibes-based guessing:

  • conn β€” The XCB connection to X11. (This one is the only one with actual words, bestie, treasure it.)
  • port β€” TODO: NOT YET DOCUMENTED.
  • drawable β€” TODO: NOT YET DOCUMENTED.
  • gc β€” TODO: NOT YET DOCUMENTED.
  • vid_x β€” TODO: NOT YET DOCUMENTED.
  • vid_y β€” TODO: NOT YET DOCUMENTED.
  • vid_w β€” TODO: NOT YET DOCUMENTED.
  • vid_h β€” TODO: NOT YET DOCUMENTED.
  • drw_x β€” TODO: NOT YET DOCUMENTED.
  • drw_y β€” TODO: NOT YET DOCUMENTED.
  • drw_w β€” TODO: NOT YET DOCUMENTED.
  • drw_h β€” TODO: NOT YET DOCUMENTED.
not the twelve consecutive TODOs 😭 she's a work in progress and we support her journey 🫢

🌈 DESCRIPTION 🌈

yeah so... the DESCRIPTION section is empty. Nothing. A whole void. The original said nothing here, so I'm saying nothing here too. That's called integrity, bestie ✨


⭐ RETURN VALUE ⭐

She hands you back an xcb_void_cookie_t. That's the tea. πŸ“

If anything goes wrong, you have to catch it yourself in the event loop β€” errors (if any) are handled there, not here.

But wait, there's more: if you'd rather handle errors directly with xcb_request_check, then use xcb_xv_get_still_checked instead. The details live in xcb-requests(3), go read her. πŸ’œ


πŸ’€ ERRORS πŸ’€

This request does never generate any errors.

fr fr. Zero. None. She is at peace. πŸ§˜β€β™€οΈ no drama, no chaos, just vibes 🌸


πŸŽ€ SEE ALSO πŸŽ€

nothing here either bestie, the original left this one blank πŸ’€


πŸ‘‘ AUTHOR πŸ‘‘

Generated from xv.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.

like, if you spot something wrong, tell the maintainers, they're lovely and they want your feedback, that's the whole point of the contact line 🫢


and that's the whole page, bestie!! go forth and call your twelve-argument function, mwah πŸ’‹

this lil rewrite came to you courtesy of X Version 11, libxcb 1.17.0 β€” catch you in the next man page, love u bye βœ¨πŸŒˆπŸ’–