Disablin xinput2 for now?

[Joerg-Cyril.Hoehle at t-systems.com]

Hi,

>There seem to be regressions in xinput2 support
I too have experienced various mouse trouble since approx. 1.3.18 on MacOS,
using XQuartz 2.5.x or 2.6.1 -- which is much more recent than any of my
Ubuntu systems (Lucid). As I've currently little time for regressions, I haven't
yet turned that into bug reports (and had always hoped that Wine release N+1
would eventually make things work again).

Haegemonia 2 aka. Legions of Iron seems to be fixed as of 1.3.22. Previously, the mouse
flickered badly when moved and it moved like crazy along one y/x direction.

As of 1.3.22, Black & White 2 doesn't react to the mouse anymore.

>should we packagers turn off 
>xinput2 support for the time being?
There's still hope that the situation will stabilize as present bug
reports are analyzed and the causes understood.

I also hope somebody will update the Wiki pages, e.g. UsefulRegistryKeys
to reflect new possibilities.  I would believe there are some.
The Wiki is the place where I'd expect to find a summary of options and
hints for when a program does not work in area Y.  I know where to look
for some forms of audio trouble, but what do I know about mouse trouble?

Before starting git bisect, I'd prefer to try out whether a few registry keys
may help with the mouse.  Which ones should I try?

Regards,
 Jörg Höhle