There seems to have been a small change in the SystemParametersInfo API call in
Win32 when Windows XP was released that is causing mouse input to be less than
happy when using SDL under Win XP. The details of it can be found here:
Basically, the 3rd parameter of SPI_SETMOUSE used to mean speed, but now it
means acceleration. Setting the 3rd parameter to 0 instead of 1 restores normal
speed to mouse input when running under Win XP.
This seems to affect the SDL app i’m working on, Project Twilight:
http://twilight.sf.net/
Any ideas on fixes for SDL, I’ve trudged through the SDL source, but can’t
exactly tell what’s going on…
-EvilTypeGuy
There seems to have been a small change in the SystemParametersInfo
API call in Win32 when Windows XP was released that is causing mouse
input to be less than happy when using SDL under Win XP. The details
of it can be found here:
http://www.quakesrc.org/?Page=form&ftp_id=922
There’s no details of the sort there. Is this the wrong URL, or am I blind? 
Basically, the 3rd parameter of SPI_SETMOUSE used to mean speed, but now it
means acceleration. Setting the 3rd parameter to 0 instead of 1 restores normal
speed to mouse input when running under Win XP.
SPI_SETMOUSE doesn’t appear ANYWHERE in the SDL source, according to
"grep -nri". Neither does SystemParametersInfo. Again, I may just be
blind.
I don’t have WinXP, so I can only be contrary, I’m afraid, but this may
not be the problem.
–ryan.
No, your eyes work just fine. There’s nothing about that there. It might
have been in a forum message, but either way there is nothing even close
to that at the URL in question. =)On Tue, Jan 01, 2002 at 11:19:50PM -0500, Ryan C. Gordon wrote:
There seems to have been a small change in the SystemParametersInfo
API call in Win32 when Windows XP was released that is causing mouse
input to be less than happy when using SDL under Win XP. The details
of it can be found here:
http://www.quakesrc.org/?Page=form&ftp_id=922
There’s no details of the sort there. Is this the wrong URL, or am I blind?
–
Joseph Carter Sanity is counterproductive
Yes, America is a country based on how pissed-off a group of taxed
people can get.
We exist as a country because we’re cheap.
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: application/pgp-signature
Size: 273 bytes
Desc: not available
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20020101/63593cb0/attachment.pgp
There seems to have been a small change in the SystemParametersInfo
API call in Win32 when Windows XP was released that is causing mouse
input to be less than happy when using SDL under Win XP. The details
of it can be found here:
http://www.quakesrc.org/?Page=form&ftp_id=922
There’s no details of the sort there. Is this the wrong URL, or am I blind?
Basically, the 3rd parameter of SPI_SETMOUSE used to mean speed, but now it
means acceleration. Setting the 3rd parameter to 0 instead of 1 restores normal
speed to mouse input when running under Win XP.
SPI_SETMOUSE doesn’t appear ANYWHERE in the SDL source, according to
"grep -nri". Neither does SystemParametersInfo. Again, I may just be
blind.
I didn’t find it either, but the behavior is the same, another project that is
using SPI_SETMOUSE thing when changed suddnely the mouse input was good again,
so I don’t know how or where this might be changed in SDL, or what might affect
it, I just know that I have two quake projects one that uses SDL for input and
one that uses the standard windows API for input, the SDL one acts funky, the
one that uses the standard windows API for input acts funky too until I change
the cool to SPI_SETMOUSE then the one that doesn’t use SDL works fine…On Tue, Jan 01, 2002 at 11:19:50PM -0500, Ryan C. Gordon wrote:
I don’t have WinXP, so I can only be contrary, I’m afraid, but this may
not be the problem.
–ryan.