SPI_GETMOUSE should work just fine, do you have a sample code which doesn't work? Is the app trying to read the registry directly without using SystemParametersInfo?
The application is the game "World In Conflict". The application is reading correctly through SystemParametersInfo().
The problem as i see it, is that there is no default value for the mouse parameters in the registry. You can see this by doing a clean wine install, and checking the registry. I think this value should have a default which should be set every time the DLL is loaded, so applications can read the value via SystemParametersInfo(). Alternatively, the DLL could detect the missing info at runtime, but that would not handle the case where the app tries to read the key directly, so i still think the first version is the best.
/p
"Peter Dons Tychsen" donpedro@tdcadsl.dk wrote:
The application is the game "World In Conflict". The application is reading correctly through SystemParametersInfo().
The problem as i see it, is that there is no default value for the mouse parameters in the registry. You can see this by doing a clean wine install, and checking the registry. I think this value should have a default which should be set every time the DLL is loaded, so applications can read the value via SystemParametersInfo(). Alternatively, the DLL could detect the missing info at runtime, but that would not handle the case where the app tries to read the key directly, so i still think the first version is the best.
SystemParametersInfo should already handle the case of missing settings in the registry providing default values. Unless you have an application which reads registry directly, so that's not a hypothetical case there is no need to fix it. Again, do you have a code snippet or a piece of relay log showing a failure?