4 ms·
I haven't used that thing but if it is as you say, it sounds backwards and very rigid, and probably only good for games (with assumptions about how the applicat
by clarry 7y ago
I haven't used that thing but if it is as you say, it sounds backwards and very rigid, and probably only good for games (with assumptions about how the application might want to use inputs).
I don't think system level APIs should ask applications anything at all.
Applications should be able to ask for inputs instead. Which is the status quo, with the caveat that there's no unified "input" API, instead there's a bunch of different APIs for keyboard, mouse, joystick, xinput gamepad, text input, midi, other kinds of input (lucky if you can find an existing API for them...). Some of these APIs multiplex a few different types of inputs, but still provide them as distinct types of events that need to be handled separately by each application.
- mmis1000 7y agoThen your program failed completely on the input device currently does not exist. How do your program know there is a controller use [w] as confirm instead of [o] when the controller does not even exist when you are writing the program? Although the new controller can just send [w] as [o], you will now have another problem that ui always ask you to press [o] when there is only [w] on the controller. Fix this problem is the sole purpose of that configurator. Don't choose the layout, just let user/system choose them. Although you could still define some preset for known device.