Closed joskuijpers closed 10 years ago
Either "primary/secondary/#" or all # for mouse button is fine (and we could refer to them the same in the Configurator); just make sure that in the end the classic API shim references the original constants MOUSE_LEFT et al.
Oh a shim would do so. But that doesn't answer the question. The actual question is: would we use the 2 mouse buttons as Primary Action, Secondary action? Then we should use primary button and secondary button. If we, in games, use the button LEFT and RIGHT. Now I think of it, we could actually have both: just need to map PRIMARY and SECONDARY to the correct LEFT or RIGHT.
"Left Mouse Button" and "Right Mouse Button" sound fine to me. They refer to what is the left and right side of the mouse.
I finally suggest: Button.LEFT and Button.Right and a configurable Button.PRIMARY and Button.SECONDARY. Which can then be used by choice. It is like using PLAYER_KEY_UP instead of KEY_W.
Instead of using 'left mouse button' and 'right mouse button', we could also use 'primary mouse button' and 'secondary mouse button', for left handed people. And because the button's function can be changed in the system settings.