6 commits

Author	SHA1	Message	Date
Tomas Jakobsson	a8fc560749	Header inclusion cleanup	2017-11-02 19:16:01 +01:00
Tomas Jakobsson	44e3e39083	Add pragma once and ifndef header guards to all headers	2017-10-31 18:12:50 +01:00
Jools Wills	3eba889bdf	Revert "workaround for analogue trigger configuration - eg with xpad."	2016-08-14 20:24:39 +01:00
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
Florian	65f2409d91	CHG: Additional input types, user-defined input config scripts	2015-06-01 20:47:42 +02:00
Aloshi	dbdbcde6cd	Renamed folders to match their projects properly.	2014-06-20 20:03:05 -05:00

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