Incorrect implementation of Input Device Coordinates

[phy_lbc]

Just wondering about what this person posted on the ML, when did it, or did this ever get fixed?

http://www.reactos.org/archives/public/ ... 11887.html

Was it supposed to be changed in wine code or straight into ROS code?

[Smiley]

Just wondering about what this person posted on the ML, when did it, or did this ever get fixed?

http://www.reactos.org/archives/public/ ... 11887.html

Was it supposed to be changed in wine code or straight into ROS code?

Hi, Ithink these problems are partly fixed. I'm also working atm to fix some of them as well. The code that has these problems in not shared with wine but we can use wine's test suite to ensur the new implementation is correct

[phy_lbc]

Oh? Because on the follow up to that post it says send a patch to fix the wine code.

http://www.reactos.org/archives/public/ ... 11893.html

So the original person didn't actually commit a patch? Was the code in his post useful?

[Haos]

AFAIK, Win32 guys are aware about this issue. I`ll doublecheck and bugzilla it if necessary. Thanks for reminding.

[Lone_Rifle]

Oh? Because on the follow up to that post it says send a patch to fix the wine code.

http://www.reactos.org/archives/public/ ... 11893.html

So the original person didn't actually commit a patch? Was the code in his post useful?

James Tabor probably didn't imply that all of the involved code was Wine's. It's more likely that James was asking the starting poster to submit patches to the relevant parts of the Wine code. Regrettably the starting poster does not have the time to actually implement the changes as he has other things to do. You could email him and offer to pay him...

[phy_lbc]

AFAIK, Win32 guys are aware about this issue. I`ll doublecheck and bugzilla it if necessary. Thanks for reminding.

Did you manage to find it on bugzilla? I did a quick check and couldn't find it. Would appreciate it if you can post the bug number.

[hto]

Filed bug 5085.