from small one page howto to huge articles all in one place
 

search text in:





Poll
Which screen resolution do you use?










poll results

Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

196713

userrating:

average rating: 1.7 (102 votes) (1=very good 6=terrible)


May 25th. 2007:
Words

486

Views

252324

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

141294

userrating:

average rating: 1.4 (42 votes) (1=very good 6=terrible)


April, 26th. 2006:

Druckversion
You are here: manpages





xcb_input_get_device_key_mapping

Section: XCB Requests (3)
Updated: libxcb 1.12
Index Return to Main Contents
 

NAME

xcb_input_get_device_key_mapping -  

SYNOPSIS

#include <xcb/xinput.h>  

Request function

xcb_input_get_device_key_mapping_cookie_t xcb_input_get_device_key_mapping(xcb_connection_t *conn, uint8_t device_id, xcb_input_key_code_t first_keycode, uint8_t count);

 

Reply datastructure


typedef struct xcb_input_get_device_key_mapping_reply_t {
    uint8_t  response_type;
    uint8_t  xi_reply_type;
    uint16_t sequence;
    uint32_t length;
    uint8_t  keysyms_per_keycode;
    uint8_t  pad0[23];
} xcb_input_get_device_key_mapping_reply_t;
 

Reply function

xcb_input_get_device_key_mapping_reply_t *xcb_input_get_device_key_mapping_reply(xcb_connection_t *conn, xcb_input_get_device_key_mapping_cookie_t cookie, xcb_generic_error_t **e);
 

Reply accessors

xcb_keysym_t *xcb_input_get_device_key_mapping_keysyms(const xcb_input_get_device_key_mapping_request_t *reply);
int xcb_input_get_device_key_mapping_keysyms_length(const xcb_input_get_device_key_mapping_reply_t *reply);
xcb_generic_iterator_t xcb_input_get_device_key_mapping_keysyms_end(const xcb_input_get_device_key_mapping_reply_t *reply);
 

REQUEST ARGUMENTS

conn
The XCB connection to X11.
device_id
TODO: NOT YET DOCUMENTED.
first_keycode
TODO: NOT YET DOCUMENTED.
count
TODO: NOT YET DOCUMENTED.
 

REPLY FIELDS

response_type
The type of this reply, in this case XCB_INPUT_GET_DEVICE_KEY_MAPPING. 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).
xi_reply_type
TODO: NOT YET DOCUMENTED.
keysyms_per_keycode
TODO: NOT YET DOCUMENTED.
 

DESCRIPTION

 

RETURN VALUE

Returns an xcb_input_get_device_key_mapping_cookie_t. Errors have to be handled when calling the reply function xcb_input_get_device_key_mapping_reply.

If you want to handle errors in the event loop instead, use xcb_input_get_device_key_mapping_unchecked. See xcb-requests(3) for details.  

ERRORS

This request does never generate any errors.  

SEE ALSO

 

AUTHOR

Generated from xinput.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
 

Index

NAME
SYNOPSIS
Request function
Reply datastructure
Reply function
Reply accessors
REQUEST ARGUMENTS
REPLY FIELDS
DESCRIPTION
RETURN VALUE
ERRORS
SEE ALSO
AUTHOR





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2020 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS : buttonmaker
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 50.7 ms