XLibre/xf86-input-joystick
1
0
Fork 0
mirror of https://github.com/X11Libre/xf86-input-joystick.git synced 2026-03-24 01:34:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated manpage to reflect keymap changes

Browse Source
This commit is contained in:
Sascha Hlusiak
2007-10-03 22:46:30 +02:00
parent c2270222a8
commit 9e8f8d54bd
1 changed files with 24 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

44
man/joystick.man
View File

@@ -76,10 +76,10 @@ Use positive and negative values to control the direction. Default: 1.0
Amplifies the movement of all axes by the given factor when pressed. Different
factors can be combined.
.TP 7
.BI "\*qkey="<keycode>[,<keycode>[,<keycode>[,<keycode>]]]
When button is pressed, a series of keydown events with the specified keycode is
generated. When the button is released, there are keyup events in the opposite
order generated. You can specify up to 4 keycodes per button.
.BI "\*qkey="<keysym>[,<keysym>[,<keysym>[,<keysym>]]]
When button is pressed, a series of keydown events with the specified keysym is
generated. When the button is released, keyup events in the opposite
order are generated. You can specify up to 4 keysyms per button.
See special section about key events below.
.TP 7
@@ -124,11 +124,12 @@ is an optional amplifier of the axis, like
.B -, +, -5, 0.4, 1.3, ...
Negative values will invert the movement. Default: 1.0
.TP 7
.BI "\*qkeylow= "<keycode>[,<keycode>[,<keycode>[,<keycode>]]]
.BI "\*qkeylow= "<keysym>[,<keysym>[,<keysym>[,<keysym>]]]
.TP 7
.BI "\*qkeyhigh="<keycode>[,<keycode>[,<keycode>[,<keycode>]]]
.BI "\*qkeyhigh="<keysym>[,<keysym>[,<keysym>[,<keysym>]]]
When the axis is moved out of the deadzone, a series of keydown events according
to the direction of the movement is generated. When the axis is released, keyup events will be generated. You can specify up to 4 keycodes for each direction.
to the direction of the movement is generated. When the axis is released, keyup
events will be generated. You can specify up to 4 keysyms for each direction.
.B keylow
defines the keys to be generated when the axis is moved in negative direction (ie. left or up),
@@ -214,38 +215,41 @@ total range of 200 pixels, 100 to the top and 100 to the bottom:
.fi
.SH "GENERATING KEY EVENTS"
Proving a \*qkey=<keycode>[,<keycode>[...]]\*q option will generate X Events with the specified keycodes in order,
Providing a \*qkey=<keysym>[,<keysym>[...]]\*q option will generate X Events with the specified keysyms
when the joystick button is pressed or the axis changed it's position. When the button/axis is released, the keys are released in the reverse order.
To lookup keycodes for KeySyms, you can use
.BR "xmodmap -pk" .
You can use unused keycodes and map them to a KeySym of your choice using xmodmap(1).
You can specify up to 4 keycodes per joystick button/axis.
The keysym parameter is defined as a numerical value, which can be looked up in the file
.IR /usr/include/X11/keysymdef.h .
You can specify up to 4 keysyms per joystick button/axis, which is useful to use modificators. Make sure you use the modificators
that are necessary to get a certain keysym.
Examples:
.nf
.BI " Option \*qMapButton1\*q \*q" "key=64,23" \*q
.BI " Option \*qMapButton1\*q \*q" "key=0xffe9,0xff09" \*q
.fi
will generate
.I "Alt_L+Tab"
when the button is pressed.
.nf
.BI " Option \*qMapButton1\*q \*q" "key=40" \*q
.BI " Option \*qMapButton1\*q \*q" "key=0xffe1,0x0064" \*q
.fi
will generate a lowercase
.IR d .
.nf
.BI " Option \*qMapButton1\*q \*q" "key=65" \*q
.BI " Option \*qMapButton1\*q \*q" "key=0x0020" \*q
.BI " Option \*qMapButton1\*q \*q" "key=32" \*q
.fi
is for the
.IR "space " key.
.nf
.BI " Option \*qMapAxis1\*q \*q" "mode=relative keylow=100 keyhigh=102 axis=0.5key" \*q
.BI " Option \*qMapAxis2\*q \*q" "mode=relative keylow=98 keyhigh=104" \*q
.BI " Option \*qMapAxis3\*q \*q" "mode=accelerated keylow=100 keyhigh=102" \*q
.BI " Option \*qMapAxis4\*q \*q" "mode=accelerated keylow=98 keyhigh=104" \*q
.BI " Option \*qMapAxis1\*q \*q" "mode=relative keylow=0xff51 keyhigh=0xff53 axis=0.5key" \*q
.BI " Option \*qMapAxis2\*q \*q" "mode=relative keylow=0xff52 keyhigh=0xff54" \*q
.BI " Option \*qMapAxis3\*q \*q" "mode=accelerated keylow=0xff51 keyhigh=0xff53" \*q
.BI " Option \*qMapAxis4\*q \*q" "mode=accelerated keylow=0xff52 keyhigh=0xff54" \*q
.fi
will map the first and third axis to the arrow keys
.IR left " and " right
@@ -267,7 +271,7 @@ will be ignored. The mode has no effect on the reported value. The axis does not
.SH "NOTES"
The driver does not do hotplugging. The joystick needs to be plugged in when the driver is loaded.
If the joystick is unplugged, the driver deactivates itself.
If the joystick is unplugged, the device will be deactivated.
.P
Make sure you add the
.I \*qSendCoreEvents\*q