7 commits

Author	SHA1	Message	Date
Jools Wills	c5b74947a0	workaround for analogue trigger configuration - eg with xpad. ... Unlike other axis, they don't default to 0, but instead start at -32768 and go to +32767 when pressed. This confuses the current ES code axis code. As a workaround, we get the initial value and if it is -32767, we add 32767 and divide by two. This gives it a range that can be handled with the current code (from 0 to 32767). Note on my X11 machine, I had to plug the joystick in after ES was loaded or it get 0 as the initial axis value for the triggers. This seems ok on the RPI though, so possible some SDL issue. With this change on a 360 controller the triggers should be correctly detected as +2 and +5 without seeing two presses for each trigger press.	2016-08-13 01:49:44 +01:00
Jools Wills	fa513e4c2d	cosmetic - spaces -> tabs to match rest of file	2016-08-10 02:48:04 +01:00
Ken Taylor	ab8409da41	Always reload input config after running onfinish script	2016-07-01 22:14:41 -07:00
Florian	65f2409d91	CHG: Additional input types, user-defined input config scripts	2015-06-01 20:47:42 +02:00
Aloshi	2926442bf0	Set hint regardless of setting (in case it is changed during run-time).	2015-01-15 17:47:31 -06:00
Felipe Otamendi	33d6733d64	Add a setting to allow for joystick input to work while not in focus.	2015-01-13 23:36:25 -02:00
Aloshi	dbdbcde6cd	Renamed folders to match their projects properly.	2014-06-20 20:03:05 -05:00

Renamed from core/src/InputManager.cpp (Browse further)