Better deadzones (#19)

Reviewed-on: #19
Co-authored-by: Anna Rose Wiggins <annabunches@gmail.com>
Co-committed-by: Anna Rose Wiggins <annabunches@gmail.com>

docs/examples/ruletypes.yml

@@ -18,8 +18,9 @@ rules:
     input:
       device: flightstick
       # To find reasonable values for your device's deadzones, use the evtest command
-      deadzone_start: 28000
-      deadzone_end: 30000
+      deadzones:
+        - start: 28000
+          end: 30000
       inverted: false
       axis: ABS_X
     output:
@@ -33,8 +34,9 @@ rules:
       # size value. This will create a deadzone that covers a range of deadzone_size,
       # centered on the center value. Note that if your deadzone_center is at the lower or upper end
       # of the axis, the total size will still be as given; the deadzone will be "shifted" into bounds.
-      deadzone_center: 29000
-      deadzone_size: 2000
+      deadzones:
+        - center: 29000
+          size: 2000
       inverted: false
       axis: Y # The ABS_ prefix is optional
     output:
@@ -46,8 +48,9 @@ rules:
       device: flightstick
       # A final way to specify deadzones is to use a size percentage instead of an absolute size.
       # This works exactly like deadzone_size, but calculates a percentage of the axis' total range.
-      deadzone_center: 29000
-      deadzone_size_percent: 5
+      deadzones:
+        - center: 29000
+          size_percent: 5
       inverted: false
       axis: Y # The ABS_ prefix is optional
     output: