Add more deadzone specification options. (#9)
Reviewed-on: #9 Co-authored-by: Anna Rose Wiggins <annabunches@gmail.com> Co-committed-by: Anna Rose Wiggins <annabunches@gmail.com>
This commit is contained in:
parent
5b9dfe0967
commit
97a1acd228
20 changed files with 344 additions and 108 deletions
|
@ -55,6 +55,16 @@ For input, you can figure out what event codes your device is emitting by runnin
|
|||
evtest | grep BTN_
|
||||
```
|
||||
|
||||
### Axis Deadzones
|
||||
|
||||
For most axis inputs, you will want to define deadzones. There are three possible approaches:
|
||||
|
||||
* Define `deadzone_start` and `deadzone_end` to explicitly set the deadzone bounds.
|
||||
* Define `deadzone_center` and `deadzone_size`; this will create a deadzone of the indicated size centered at the given axis position.
|
||||
* Define `deadzone_center` and `deadzone_size_percent` to use a percentage of the total axis size.
|
||||
|
||||
See <examples/ruletypes.yml> for usage examples.
|
||||
|
||||
## Modes
|
||||
|
||||
Modes are optional, and also have the simplest configuration. To define modes, add this to your configuration:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue