Scott Pleb 0bede93daa evdev: Correctly calculate axis range for min values greater than 0. ... Axis range was previously calculated as max + abs(min), which relies on the assumption that min will not exceed 0. For (min, max) values like (0, 255) or (-128, 127), which I assume to be the most common cases, the range is correctly calculated as 255. However, given (20, 235), the range is erroneously calculated as 255, leading to axis values being normalized incorrectly. SDL already handles this case correctly. After changing the range calculation to max - min, the axis values received from the evdev backend are practically identical to the values received from the SDL backend.		2017-11-11 02:07:04 -05:00
..
Android
DInput	Fix minor formatting issues	2017-06-05 02:32:19 +02:00
evdev	evdev: Correctly calculate axis range for min values greater than 0.	2017-11-11 02:07:04 -05:00
ForceFeedback
OSX	Prevent multiple HID elements of same usage type on OSX	2017-09-15 19:19:46 +02:00
Pipes	StringUtil: Make SplitString return by value	2017-06-11 16:48:20 +02:00
Quartz	Add headless support on macOS	2017-04-15 19:34:42 -07:00
SDL
XInput	Ignore capabilities reported by an XInput device	2017-08-09 22:51:01 -05:00
Xlib
ControllerInterface.cpp
ControllerInterface.h	Add missing "functional" include	2017-02-20 14:25:55 +00:00
Device.cpp	Device: Provide operator!= counterparts to operator== for DeviceQualifier	2017-06-03 19:34:35 -04:00
Device.h	Device: Provide operator!= counterparts to operator== for DeviceQualifier	2017-06-03 19:34:35 -04:00