I also haven't tested with various other controllers.I’ve always had a secret desire to be able to program computers… the problem is it’s not something you can do just like that! I can recall starting off with a Commodore PET 2001 some time in the late 70’s and I can remember how enjoyable it was to be able to create simple scripts that could react to whatever you pressed on the keyboard. I *think* the limitation applies to all of these But I haven't actually tested with all controller variants there. At least for controllers from Microsoft and some other big names. I say "something like" above because ideally the new text should have an evidence-based and exact description of which game controllers this limitation does and does not apply to. GetKeyState can read JoyName, JoyButtons, JoyAxes and JoyInfo even when an AutoHotkey window is not active.Īlso add such a green box in the "Important notes" section here
To detect those controller inputs for other active windows use the XInput.ahk library
This limitation also applies to GetKeyState() for Joy1 to Jo圓2 and JoyX, JoyY, JoyZ, JoyR, JoyU. Note: For Xbox controllers from 2013 or newer (anything newer than Xbox 360 controllers) hotkeys Joy1 to Jo圓2 only work when an AutoHotkey window is active. So if the term 'game controller' is adopted a short explanation of why the phrase 'Joy' is still used must also be added. One complication is that built in hotkeys like Joy1 should not change, since that would break code backward compatibility. Suggestion 1: change to 'Game controller' or 'controller' in (sub)headings and text that currently use 'Joystick'. The most common types of game controllers today are of the gamepad type so do not look like the tall joysticks of old. But today joystick more commonly refer narrowly to input devices with a tall stick ( ) and the term 'game controller' or simply 'controller' is used for game input devices more broadly. Use term 'Game controller' instead of 'Joystick'ĪutoHotkey v2 documentation (just like v1) uses 'Joystick' as term for game input devices.
0 kommentar(er)
