1xcb_dpms_capable(3) XCB Requests xcb_dpms_capable(3)
2
3
4
6 xcb_dpms_capable -
7
9 #include <xcb/dpms.h>
10
11 Request function
12 xcb_dpms_capable_cookie_t xcb_dpms_capable(xcb_connection_t *conn,
13
14 Reply datastructure
15 typedef struct xcb_dpms_capable_reply_t {
16 uint8_t response_type;
17 uint8_t pad0;
18 uint16_t sequence;
19 uint32_t length;
20 uint8_t capable;
21 uint8_t pad1[23];
22 } xcb_dpms_capable_reply_t;
23
24 Reply function
25 xcb_dpms_capable_reply_t
26 *xcb_dpms_capable_reply(xcb_connection_t *conn,
27 xcb_dpms_capable_cookie_t cookie, xcb_generic_error_t **e);
28
30 conn The XCB connection to X11.
31
33 response_type
34 The type of this reply, in this case XCB_DPMS_CAPABLE. This
35 field is also present in the xcb_generic_reply_t and can be
36 used to tell replies apart from each other.
37
38 sequence The sequence number of the last request processed by the X11
39 server.
40
41 length The length of the reply, in words (a word is 4 bytes).
42
43 capable TODO: NOT YET DOCUMENTED.
44
47 Returns an xcb_dpms_capable_cookie_t. Errors have to be handled when
48 calling the reply function xcb_dpms_capable_reply.
49
50 If you want to handle errors in the event loop instead, use
51 xcb_dpms_capable_unchecked. See xcb-requests(3) for details.
52
54 This request does never generate any errors.
55
58 Generated from dpms.xml. Contact xcb@lists.freedesktop.org for correcā
59 tions and improvements.
60
61
62
63X Version 11 libxcb 1.13.1 xcb_dpms_capable(3)