In every issue or conversation we use completely different naming for each item so it could be nice to have a consistent naming across all the code and conversations so we really understand that we are talking about the same things :D
I'm totally open here, if you have suggestion or if you prefer to go for a similar naming as the one used on Steam Controller API, I'm ok with that.
In every issue or conversation we use completely different naming for each item so it could be nice to have a consistent naming across all the code and conversations so we really understand that we are talking about the same things :D I'm totally open here, if you have suggestion or if you prefer to go for a similar naming as the one used on Steam Controller API, I'm ok with that.
Looking at the current implementation:
rename to
inputActionSet. So
currentInputMappingshould be renamed to
currentInputSet`.task1
,task2
:actions
type
: digital, analog1d, analog2d, analog3d, pose,...bindings
:triggerdown
is binded tolefthand
.activators
: Modifiers of an specific input event: longpress, doubletouch, doublepress.behaviours
: Add a custom behaviour to a input element, likedpad
to athumbpad
.trackpad
todpad
is what steam callsmode
.