Mon, 11 Feb 2013 18:28:05 -0800Hopefully fixed the last of the C variable declaration problems which caused compile failures with Visual Studio.
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 18:28:05 -0800] rev 6854
Hopefully fixed the last of the C variable declaration problems which caused compile failures with Visual Studio.

Mon, 11 Feb 2013 18:22:32 -0800Fixed double-default case
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 18:22:32 -0800] rev 6853
Fixed double-default case

Mon, 11 Feb 2013 18:22:17 -0800Fixed compiling SYN_DROPPED with older kernel headers
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 18:22:17 -0800] rev 6852
Fixed compiling SYN_DROPPED with older kernel headers

Mon, 11 Feb 2013 18:18:34 -0800Fixed compiler warnings
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 18:18:34 -0800] rev 6851
Fixed compiler warnings

Mon, 11 Feb 2013 18:13:52 -0800Fixed C variable declarations
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 18:13:52 -0800] rev 6850
Fixed C variable declarations

Mon, 11 Feb 2013 17:40:09 -0800Backed out use of @autorelease keyword for now, since it's not supported by older Xcode versions.
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 17:40:09 -0800] rev 6849
Backed out use of @autorelease keyword for now, since it's not supported by older Xcode versions.

Mon, 11 Feb 2013 17:39:52 -0800Backed out use of @autorelease keyword for now, since it's not supported by older Xcode versions.
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 17:39:52 -0800] rev 6848
Backed out use of @autorelease keyword for now, since it's not supported by older Xcode versions.

Mon, 11 Feb 2013 17:25:58 -0800Fixed compiler warning (and undefined behavior) in game controller event filter.
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 17:25:58 -0800] rev 6847
Fixed compiler warning (and undefined behavior) in game controller event filter.

Mon, 11 Feb 2013 17:02:13 -0800Workaround for NVIDIA bug in glXSwapIntervalEXT.
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 17:02:13 -0800] rev 6846
Workaround for NVIDIA bug in glXSwapIntervalEXT.

This works around a bug in NVIDIA's implementation of
glXSwapIntervalEXT, where it ignores updates to what it *thinks* is the
current value, even though glXQueryDrawable returns a different value.

Bug reported to NVIDIA and will hopefully be a part of 319.xx.

Also a fix for invalidly treating glXSwapIntervalEXT as having an int
return value (it's void).

Mon, 11 Feb 2013 16:51:00 -0800Patch - Joystick coef[] doesn't support dial with low number of positions.
Sam Lantinga <slouken@libsdl.org> [Mon, 11 Feb 2013 16:51:00 -0800] rev 6845
Patch - Joystick coef[] doesn't support dial with low number of positions.

Simon <simon@mungewell.org>

I am working on joystick support for the SRW-S1 gaming wheel on Linux,
this device has 3 dials with only a few positions each.

At present SDL2 only fail to report the highest position value, due to the
interger math used for coef[]'s.

So with a 4 position switch I have input values (with evtest)
--
Event: time 1358967246.173186, type 3 (EV_ABS), code 9 (ABS_GAS), value 2
Event: time 1358967246.173186, -------------- SYN_REPORT ------------
Event: time 1358967246.369150, type 3 (EV_ABS), code 9 (ABS_GAS), value 1
Event: time 1358967246.369150, -------------- SYN_REPORT ------------
Event: time 1358967246.930277, type 3 (EV_ABS), code 9 (ABS_GAS), value 0
Event: time 1358967246.930277, -------------- SYN_REPORT ------------
Event: time 1358967249.369832, type 3 (EV_ABS), code 9 (ABS_GAS), value 1
Event: time 1358967249.369832, -------------- SYN_REPORT ------------
Event: time 1358967249.514382, type 3 (EV_ABS), code 9 (ABS_GAS), value 2
Event: time 1358967249.514382, -------------- SYN_REPORT ------------
Event: time 1358967249.626189, type 3 (EV_ABS), code 9 (ABS_GAS), value 3
Event: time 1358967249.626189, -------------- SYN_REPORT ------------
--

Testjoystick reports
--
Joystick has 6 axes, 1 hats, 0 balls, and 17 buttons
Joystick 0 axis 5 value: 32767
Joystick 0 axis 5 value: 0
Joystick 0 axis 5 value: -32768
Joystick 0 axis 5 value: 0
Joystick 0 axis 5 value: 32767
Joystick 0 axis 5 value: 0
Joystick 0 axis 5 value: -32768
--

The attached patch 'shifts' the coef[], so that 1/2 values can be
computed/seen and allows testjoystick to report correctly.
--
Joystick has 6 axes, 1 hats, 0 balls, and 17 buttons
Joystick 0 axis 5 value: -10923
Joystick 0 axis 5 value: 10922
Joystick 0 axis 5 value: 32767
Joystick 0 axis 5 value: 10922
Joystick 0 axis 5 value: -10923
Joystick 0 axis 5 value: -32768
Joystick 0 axis 5 value: -10923
Joystick 0 axis 5 value: 10922
Joystick 0 axis 5 value: 32767
--

Cheers,
Simon