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