Query: xcb_input_get_feedback_control_unchecked
OS: centos
Section: 3
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
xcb_input_get_feedback_control(3) XCB Requests xcb_input_get_feedback_control(3)NAMExcb_input_get_feedback_control -SYNOPSIS#include <xcb/xinput.h> Request function xcb_input_get_feedback_control_cookie_t xcb_input_get_feedback_control(xcb_connection_t *conn, uint8_t device_id); Reply datastructure typedef struct xcb_input_get_feedback_control_reply_t { uint8_t response_type; uint8_t pad0; uint16_t sequence; uint32_t length; uint16_t num_feedback; uint8_t pad1[22]; } xcb_input_get_feedback_control_reply_t; Reply function xcb_input_get_feedback_control_reply_t *xcb_input_get_feedback_control_reply(xcb_connection_t *conn, xcb_input_get_feedback_control_cookie_t cookie, xcb_generic_error_t **e);REQUEST ARGUMENTSconn The XCB connection to X11. device_id TODO: NOT YET DOCUMENTED.REPLY FIELDSresponse_type The type of this reply, in this case XCB_INPUT_GET_FEEDBACK_CONTROL. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. sequence The sequence number of the last request processed by the X11 server. length The length of the reply, in words (a word is 4 bytes). num_feedback TODO: NOT YET DOCUMENTED.DESCRIPTIONRETURN VALUEReturns an xcb_input_get_feedback_control_cookie_t. Errors have to be handled when calling the reply function xcb_input_get_feedback_con- trol_reply. If you want to handle errors in the event loop instead, use xcb_input_get_feedback_control_unchecked. See xcb-requests(3) for details.ERRORSThis request does never generate any errors.SEE ALSOAUTHORGenerated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.XCB2014-06-10 xcb_input_get_feedback_control(3)
Similar Topics in the Unix Linux Community |
---|
Best performance UNIX just for HOST Virtualization? |
Tar Command |
CentOS 6 ran out of space, need to reclaim it |
Controlling user input |
Please Welcome Dave Munro to the Moderator Team! |