Disablin xinput2 for now?

[Vitaliy Margolen]

On 06/20/2011 08:36 AM, Alexandre Julliard wrote:
> Vitaliy Margolen<wine-devel at kievinfo.com>  writes:
>
>> On 06/20/2011 02:55 AM, Marcus Meissner wrote:
>>> As this might be a X.org issue, should we packagers turn off
>>> xinput2 support for the time being?
>>
>> If that will fix all dinput regressions - absolutely. Or add a
>> registry option to disable xinput2.
>
> It will of course fix some regressions, and introduce new ones for
> things that have been fixed by the changes. Don't tell me that dinput
> was working perfectly before. And there is a registry option (GrabPointer).
>
Dinput never perfectly worked before and doesn't work perfectly now. Even 
native has serious issues in Wine.

I've lost track of all the changes you did to mouse/keyboard events, ll 
hooks, pointer position changes, etc. But it seems to me something broke 
that was working before. At least did not affect programs as much as it does 
now.

I've seen number of programs/games that were highly sensitive to timing and 
order of various events. Unfortunately it was impossible to exactly 
replicate and/or make a test for it. And with dynamic nature of the problem 
it's a royal PITA to debug.

In either case, it seems that what used to more-less work before doesn't 
work at all. Or has major problems (non-xinput2 code-path). And the new 
xinput2 code-path while resolving large number of issues, introduced number 
of other problems.

So just disabling xinput2 support in any a binary build won't really help much.

Vitaliy.