@ -70,71 +70,44 @@ When the ADC reads 900 or higher, the returned axis value will be -127, whereas
In this example, the first axis will be read from the `A4` pin while `B0` is set high and `A7` is set low, using `analogReadPin()`, whereas the second axis will not be read.
In this example, the first axis will be read from the `A4` pin while `B0` is set high and `A7` is set low, using `analogReadPin()`, whereas the second axis will not be read.
In order to give a value to the second axis, you can do so in any customizable entry point: as an action, in `process_record_user()` or in `matrix_scan_user()`, or even in `joystick_task()` which is called even when no key has been pressed.
#### Virtual Axes
You assign a value by writing to `joystick_status.axes[axis_index]` a signed 8-bit value (ranging from -127 to 127). Then it is necessary to assign the flag `JS_UPDATED` to `joystick_status.status` in order for an updated HID report to be sent.
The following example writes two axes based on keypad presses, with `KC_P5` as a precision modifier:
To give a value to virtual axes, call `joystick_set_axis(axis, value)`.
The following example adjusts two virtual axes (X and Y) based on keypad presses, with `KC_P5` as a precision modifier:
joystick_position+=(clockwise?2:-2)*(full_joystick_value/pulses_per_revolution);// +2 and -2 are used, since +1.0 and -1.0 axis output refers to positions at half of a full rotation
joystick_position+=(clockwise?2:-2)*(full_joystick_value/pulses_per_revolution);// +2 and -2 are used, since +1.0 and -1.0 axis output refers to positions at half of a full rotation