Re: Re: mouse cursor problems

> This should help identify the problem with the cursor:
> 1. Symptom: Cursor snaps back to the top left hand corner of the screen.
>    Problem: WineX supplies relative information.  The game thinks it is 
>             receiving absolute information.
> 2. Symptom: Cursor gets stuck at the bottom right corner of the screen.
>    Problem: WineX supplies absolute information.  The game thinks it is 
>             receiving relative information.  
> 3. Symptom: Cursor snaps to the center of the screen.
>    Problem: This is a warping problem.  The X server draws the cursor but
>             WineX believes the game is drawing the cursor.
>  
> The first 2 problems are IMO a result of a misinterpretation of the dinput
> specs (the dinput debugging is most valuable).  The third is purely a 
> WineX problem.

Thanks for pointing me in the right direction. As the game I am using
was reported to work in 3.1, I took a look at the dlls/dinput/mouse code
and diffed the 3.1 branch to the current HEAD in CVS. I don't know
enough about the code to attempt a patch, but it appears that the "if
(wparam == WM_MOUSEMOVE) {" block is the right place to look. I
espically liked the comment: "/* Relative mouse input with absolute
mouse event : the real fun starts here... */" :)

http://cvs.transgaming.org/cgi-bin/viewcvs.cgi/winex/dlls/dinput/mouse/main.c?only_with_tag=winex-3-1&r1=1.37.2.1%3Awinex-3-1&tr1=&r2=1.46%3AHEAD&tr2=&diff_format=l

Greg
-