That is, each and every developer who wants to allow for an assignable scroll wheel. I imagine we'll have to have a dropdown option which offers a number of commands to the Scroll Up function and a dropdown option which offers a number of commands to the Scroll Down function.Īnd then that binding wouldn't be serializable for storage and retrieval viaĪctions.LoadBindingOverridesFromJson(jsonKeyBinds) So let's say we follow your insinuation and leave this vital feature out and read the axis values from the scroll wheel and do the reverse - that is, to grant people the ability of assigning a command to to a controlinstead of what the whole world is used to, which is assigning a control to a command. So what do you propose in place of this for us to use? InputAction.PerformInteractiveRebinding(bindingIndex) to rebind actions. Without the scroll up and down 'keys' we can't make use of

Once you try and add functionality to your app where the user can choose to dynamically rebind the scroll up and scroll down inputs to their commands (such as for weapon switching, consumable item switching) you are going to need this too.

Click to expand.And a gamepad joystick offers separated axes, float values AND discrete buttons which are assignable to user-rebindable commands.

Imagine 1.3.0 for apple instal