xcb_xf86dri_destroy_context(3) centos man page | unix.com

Man Page: xcb_xf86dri_destroy_context

Operating Environment: centos

Section: 3

xcb_xf86dri_destroy_context(3)					   XCB Requests 				    xcb_xf86dri_destroy_context(3)

NAME
xcb_xf86dri_destroy_context -
SYNOPSIS
#include <xcb/xf86dri.h> Request function xcb_void_cookie_t xcb_xf86dri_destroy_context(xcb_connection_t *conn, uint32_t screen, uint32_t context);
REQUEST ARGUMENTS
conn The XCB connection to X11. screen TODO: NOT YET DOCUMENTED. context 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_xf86dri_destroy_context_checked. See xcb-requests(3) for de- tails.
ERRORS
This request does never generate any errors.
SEE ALSO
AUTHOR
Generated from xf86dri.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
XCB
2014-06-10 xcb_xf86dri_destroy_context(3)
Related Man Pages
xcb_glx_create_new_context(3) - centos
xcb_glx_create_pixmap(3) - centos
xcb_record_create_context(3) - centos
xcb_record_create_context_checked(3) - centos
xcb_record_register_clients(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?
Unsure why access time on a directory change isn't changing
Controlling user input