I just bumped the windib target to a higher priority than the directx
one in CVS.
This should fix everyone’s DirectDraw/DirectInput issues at a possible
performance hit for blit speed in some cases.
If you were exclusively using 2D software surfaces or OpenGL, you are
likely to not notice any change.
If you have an SDL-based Windows project, please upgrade to the latest
in CVS and let me know if this makes things better or worse for you.
This change may just be a temporary workaround, depending on the
feedback I get.
You can still enable DirectDraw with the SDL_VIDEODRIVER enviroment
variable.
–ryan.
This has fixed input issues for me using Windows x64
Is there any workaround yet for the no in-line ASM on the AMD64 platform yet? Currently I’ve just disabled sdl_stretch to compile under x64, which is the only in-line ASM I have run into thus far. The application I used to test it with uses OpenGL, so no real losses that I can see, I haven’t experienced any input errors yet (dxinput would give errors previously posted, disallowing keyboard usage completely).
–William
Is there any workaround yet for the no in-line ASM on the AMD64 platform
yet? Currently I’ve just disabled sdl_stretch to compile under x64,
which is the only in-line ASM I have run into thus far. The application
I used to test it with uses OpenGL, so no real losses that I can see, I
haven’t experienced any input errors yet (dxinput would give errors
previously posted, disallowing keyboard usage completely).
MSVC doesn’t allow inline asm in Win64 programs…this code would have
to be made 64-bit clean and moved to an external .asm file that MASM (or
whatever) can build.
Does anyone know if there’s a 64-bit Cygwin yet? 
–ryan.