- This reduces the number of types associated with input; adding a
distinct input type doesn't introduce a whole new enumerated type
and related functions.
- Special handling for different devices is needed less often. If you
want to respond to an F1 press, simply check for KEY_F1; the device
type doesn't really matter (though it'll usually be a keyboard).
- This allows cleaner support for generalized USB devices. While they're
usually of the traditional classes (keyboard, joystick) with associated
inputs, they don't have to be.
- Forced casts between parallel types can be removed, and weakly-specified
variables (ints instead of the enum type) can be fixed.
Some things that might have been merged havn't; for example, arrow keys
on a keyboard (KEY_UP) are still distinct from axes on a joystick (JOY_UP).
These may or may not be merged in the future.
Some were: removed PUMP_ symbols. Treat them as generic buttons, and just
give them names with GetDeviceSpecificInputString. It's not worth
introducing more special names for something only used in one place.
the standard had already been released. What's the point of having
standard language abbreviations if they're subject to change?
"Annex B" in ISO 639-1:2001 (over a decade later, if that's a year) says
"The changes were publicised, but they have not been included in printed
versions of ISO 639." The first google hit for ISO-639 still makes no mention
of these changes (http://www.w3.org/WAI/ER/IG/ert/iso639.htm). That rules.
Remove "XS?"; as far as I can tell that's just an error in the "native language"
page.
Glenn Maynard