As per the PR, the changes still holding it up. Add onekey for testing. Fix ARM builds. Fix device descriptor when either axes or buttons is zero. Add compile-time check for at least one axis or button. Move definition to try to fix conflict. PR review comments. qmk cformatgc_switch
parent
d88bdc6a1b
commit
801be60473
@ -0,0 +1,5 @@ |
||||
#include QMK_KEYBOARD_H |
||||
|
||||
const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = { |
||||
LAYOUT( JS_BUTTON0 ) |
||||
}; |
@ -1,15 +1,13 @@ |
||||
#include "joystick.h" |
||||
|
||||
joystick_t joystick_status = {
|
||||
.buttons = {0}, |
||||
.axes = { |
||||
joystick_t joystick_status = {.buttons = {0}, |
||||
.axes = |
||||
{ |
||||
#if JOYSTICK_AXES_COUNT > 0 |
||||
0 |
||||
#endif |
||||
}, |
||||
.status = 0 |
||||
}; |
||||
.status = 0}; |
||||
|
||||
// array defining the reading of analog values for each axis
|
||||
__attribute__ ((weak)) |
||||
joystick_config_t joystick_axes[JOYSTICK_AXES_COUNT] = {}; |
||||
__attribute__((weak)) joystick_config_t joystick_axes[JOYSTICK_AXES_COUNT] = {}; |
||||
|
Loading…
Reference in new issue