TODO
author Sam Lantinga <slouken@libsdl.org>
Thu, 02 Apr 2009 04:43:36 +0000
branchSDL-1.2
changeset 4167 a6f635e5eaa6
parent 1621 f12379c41042
child 1654 0a53c90a37f9
child 1895 c121d94672cb
permissions -rw-r--r--
Fixed bug #611

From Tim Angus 2008-08-12 11:18:06

I'm one of the maintainers of ioquake3.org, an updated version of the
Quake 3 engine. Relatively recently, we moved ioq3 to use SDL as a
replacement for 95% of the platform specific code that was there. On the
whole it's doing a great job but unfortunately since the move we've been
getting complaints about the quality of the mouse input on the Windows
platform to the point where for many the game is unplayable. Put in
other terms, the current stable SDL 1.2 is basically not fit for purpose
if you need high quality mouse input as you do in a first person shooter.

Over the weekend I decided to pull my finger out and actually figure out
what's going on. There are basically two major problems. Firstly, when
using the "windib" driver, mouse input is gathered via the WM_MOUSEMOVE
message. Googling for this indicates that often this is known to result
in "spurious" and/or "missing" mouse movement events; this is the
primary cause of the poor mouse input. The second problem is that the
"directx" driver does not work at all in combination with OpenGL meaning
that you can't use DirectInput if your application also uses OpenGL. In
other words you're locked into using the "windib" driver and its poor
mouse input.

In order to address these problems I've done the following:

* Remove WM_MOUSEMOVE based motion event generation and replace with
calls to GetCursorPos which seems much more reliable. In order to
achieve this I've moved mouse motion out into a separate function that
is called once per DIB_PumpEvents.

* Remove the restriction on the "directx" driver being inoperable in
combination with OpenGL. There is a bug for this issues that I've
hijacked to a certain extent
(http://bugzilla.libsdl.org/show_bug.cgi?id=265). I'm the first to admit
I don't really understand why this restriction is there in the first
place. The commit message for the bug fix that introduced this
restriction (r581) isn't very elaborate and I couldn't see any other bug
tracking the issue. If anyone has more information on the bug that was
avoided by r581 it would be helpful as I/someone could then look into
addressing the problem without disabling the "directx" driver.

* I've also removed the restriction on not being allowed to use
DirectInput in windowed mode. I couldn't see any reason for this, at
least not from our perspective. I have my suspicions that it'll be
something like matching up the cursor with the mouse coordinates...

* I bumped up the DirectInput API used to version 7 in order to get
access to mouse buttons 4-7. I've had to inject a little bit of the DX7
headers into SDL there as the MinGW ones aren't up to date in this respect.
slouken@0
     1
slouken@0
     2
Wish list for the 1.3 development branch:
slouken@1534
     3
http://bugzilla.libsdl.org/
slouken@0
     4
slouken@0
     5
 * Add mousewheel events (new unified event architecture?)
slouken@0
     6
 * DirectInput joystick support needs to be implemented
slouken@0
     7
 * Be able to enumerate and select available audio and video drivers
slouken@1621
     8
 * Fullscreen video mode support for Mac OS X
slouken@0
     9
 * Explicit vertical retrace wait (maybe separate from SDL_Flip?)
slouken@0
    10
 * Shaped windows, windows without borders
slouken@0
    11
 * Multiple windows, multiple display support
slouken@0
    12
 * SDL_INIT_EVENTTHREAD on Windows and MacOS?
slouken@0
    13
 * Add a timestamp to events
slouken@0
    14
 * Add audio input API
slouken@2
    15
 * Add hardware accelerated scaled blit
slouken@2
    16
 * Add hardware accelerated alpha blits
slouken@2
    17
 * Redesign blitting architecture to allow blit plugins
slouken@0
    18
slouken@0
    19
In the jump from 1.2 to 1.3, we should change the SDL_Rect members to
slouken@0
    20
int and evaluate all the rest of the datatypes.  This is the only place
slouken@0
    21
we should do it though, since the 1.2 series should not break binary
slouken@0
    22
compatibility in this way.
slouken@150
    23
slouken@150
    24
Requests:
slouken@150
    25
 * PCM and CDROM volume control (deprecated, but possible)