|
NAMExcb_selinux_get_window_context -SYNOPSIS#include <xcb/xselinux.h>Request functionxcb_selinux_get_window_context_cookie_t xcb_selinux_get_window_context(xcb_connection_t *conn, xcb_window_t window); Reply datastructuretypedef struct xcb_selinux_get_window_context_reply_t { uint8_t response_type; uint8_t pad0; uint16_t sequence; uint32_t length; uint32_t context_len; uint8_t pad1[20]; } xcb_selinux_get_window_context_reply_t; Reply functionxcb_selinux_get_window_context_reply_t *xcb_selinux_get_window_context_reply(xcb_connection_t *conn, xcb_selinux_get_window_context_cookie_t cookie, xcb_generic_error_t **e); Reply accessorschar *xcb_selinux_get_window_context_context(const xcb_selinux_get_window_context_request_t *reply); int xcb_selinux_get_window_context_context_length(const xcb_selinux_get_window_context_reply_t *reply); xcb_generic_iterator_t
xcb_selinux_get_window_context_context_end(const
xcb_selinux_get_window_context_reply_t *reply);
REQUEST ARGUMENTS
REPLY FIELDS
DESCRIPTIONRETURN VALUEReturns an xcb_selinux_get_window_context_cookie_t. Errors have to be handled when calling the reply function xcb_selinux_get_window_context_reply.If you want to handle errors in the event loop instead, use xcb_selinux_get_window_context_unchecked. See xcb-requests(3) for details. ERRORSThis request does never generate any errors.SEE ALSOAUTHORGenerated from xselinux.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
Visit the GSP FreeBSD Man Page Interface. |