Techwizz/xboxdrv
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Added ebnf description for --ui-buttonmap and --ui-axismap

Browse source
This commit is contained in:
Ingo Ruhnke 2010-05-23 16:15:58 +02:00
parent ed62317ebf
commit 9f84e52d35
2 changed files with 45 additions and 4 deletions

27
doc/xboxdrv.1
View file

@ -349,7 +349,19 @@ Possible axis names are: x1, y1, x2, y2, lt, rt
Swaping lt or rt with x1, y1, x2, y2 will not work properly, since
their range is different.
.TP
\*(T<\fB\-\-ui\-buttonmap\fR\*(T> \fIBUTTON=UIBUTTONSPEC,...\fR
\*(T<\fB\-\-ui\-buttonmap\fR\*(T> \fIUIBUTTONSPEC,...\fR
.nf
\*(T<UIBUTTONSPEC ::= BUTTON, [ "+", BUTTON ], "=", RELSPEC | BTNSPEC
RELSPEC ::= [ DEVICEID ], "REL_", [ ":", [ VALUE ], [ ":", REPEAT ] ]
BTNSPEC ::= [ DEVICEID ], "BTN_", NAME | "KEY_", NAME, { "+", BTNSPEC }
BUTTON ::= "a" | "b" | "x" | "y" | "lb" | "rb" | "lt" | "rt" |
"tl" | "tr" | "start" | "select" | "guide"
NAME ::= STRING
VALUE ::= NUMBER
REPEAT ::= NUMBER
DEVICEID ::= NUMBER\*(T>
.fi
Allows you to change the event code that is send to the
kernel for buttons. The usage is similar to the normal button
mapping, except that the right hand side is an event name from
@ -450,7 +462,18 @@ See the section KEYBOARD EMULATION below on how to
resolve issues with Xorg not detecting the virtual
keyboard that xboxdrv creates.
.TP
\*(T<\fB\-\-ui\-axismap\fR\*(T> \fIAXIS=UIAXISSPEC,...\fR
\*(T<\fB\-\-ui\-axismap\fR\*(T> \fIUIAXISSPEC,...\fR
.nf
\*(T<UIAXISSPEC ::= AXIS, "=", RELSPEC | BTNSPEC | ABSSPEC
BTNSPEC ::= "KEY_", NAME, ":", "KEY_", NAME, ":", "THRESHOLD"
RELSPEC ::= "REL_", NAME, ":", VALUE, ":", "REPEAT"
ABSSPEC ::= "ABS_", NAME
AXIS ::= "x1", "y1", "x2", "y2", "z", "lt", "rt"
VALUE ::= NUMBER
REPEAT ::= NUMBER
NAME ::= STRING\*(T>
.fi
Similar to \*(T<\fB\-\-ui\-buttonmap\fR\*(T> this option
allows you to change the event code that is send to the
kernel for axes. The events that are available are the

22
doc/xboxdrv.xml
View file

@ -466,8 +466,17 @@
</varlistentry>
<varlistentry>
<term><option>--ui-buttonmap</option> <replaceable class="parameter">BUTTON=UIBUTTONSPEC,...</replaceable></term>
<term><option>--ui-buttonmap</option> <replaceable class="parameter">UIBUTTONSPEC,...</replaceable></term>
<listitem>
<programlisting><![CDATA[UIBUTTONSPEC ::= BUTTON, [ "+", BUTTON ], "=", RELSPEC | BTNSPEC
RELSPEC ::= [ DEVICEID ], "REL_", [ ":", [ VALUE ], [ ":", REPEAT ] ]
BTNSPEC ::= [ DEVICEID ], "BTN_", NAME | "KEY_", NAME, { "+", BTNSPEC }
BUTTON ::= "a" | "b" | "x" | "y" | "lb" | "rb" | "lt" | "rt" |
"tl" | "tr" | "start" | "select" | "guide"
NAME ::= STRING
VALUE ::= NUMBER
REPEAT ::= NUMBER
DEVICEID ::= NUMBER]]></programlisting>
<para>
Allows you to change the event code that is send to the
kernel for buttons. The usage is similar to the normal button
@ -576,8 +585,17 @@
</varlistentry>
<varlistentry>
<term><option>--ui-axismap</option> <replaceable class="parameter">AXIS=UIAXISSPEC,...</replaceable></term>
<term><option>--ui-axismap</option> <replaceable class="parameter">UIAXISSPEC,...</replaceable></term>
<listitem>
<programlisting><![CDATA[UIAXISSPEC ::= AXIS, "=", RELSPEC | BTNSPEC | ABSSPEC
BTNSPEC ::= "KEY_", NAME, ":", "KEY_", NAME, ":", THRESHOLD
RELSPEC ::= "REL_", NAME, ":", VALUE, ":", REPEAT
ABSSPEC ::= "ABS_", NAME
AXIS ::= "x1", "y1", "x2", "y2", "z", "lt", "rt"
VALUE ::= NUMBER
REPEAT ::= NUMBER
THRESHOLD ::= NUMBER
NAME ::= STRING]]></programlisting>
<para>
Similar to <option>--ui-buttonmap</option> this option
allows you to change the event code that is send to the