xcb_xvmc_destroy_context_checked(3) centos man page | unix.com

Man Page: xcb_xvmc_destroy_context_checked

Operating Environment: centos

Section: 3

xcb_xvmc_destroy_context(3)					   XCB Requests 				       xcb_xvmc_destroy_context(3)

NAME
xcb_xvmc_destroy_context -
SYNOPSIS
#include <xcb/xvmc.h> Request function xcb_void_cookie_t xcb_xvmc_destroy_context(xcb_connection_t *conn, xcb_xvmc_context_t context_id);
REQUEST ARGUMENTS
conn The XCB connection to X11. context_id TODO: NOT YET DOCUMENTED.
DESCRIPTION
RETURN VALUE
Returns an xcb_void_cookie_t. Errors (if any) have to be handled in the event loop. If you want to handle errors directly with xcb_request_check instead, use xcb_xvmc_destroy_context_checked. See xcb-requests(3) for de- tails.
ERRORS
This request does never generate any errors.
SEE ALSO
AUTHOR
Generated from xvmc.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
XCB
2014-06-10 xcb_xvmc_destroy_context(3)
Related Man Pages
xcb_change_pointer_control(3) - centos
xcb_input_ungrab_device_key(3) - centos
xcb_input_ungrab_device_key_checked(3) - centos
xcb_randr_set_crtc_transform(3) - centos
xcb_x_print_create_context_checked(3) - centos
Similar Topics in the Unix Linux Community
Weird 'find' results
Set hard block limit for user using quota
Best performance UNIX just for HOST Virtualization?
CentOS7 restoring file capabilities
Unsure why access time on a directory change isn't changing