XInput 2 for Wine - now X11R7.5 is at release candidate...

aoanla · Post by **aoanla** » Sun Oct 18, 2009 5:14 am

Hello everyone,

I recall, around when XInput 2 was first being discussed as imminent (and, due to the nature of the X release process, turned out not to be), some initial work was done on implementing "proper" relative mouse movement using it.

I can't seem to find any record of it after the first implementation was thrown out to the dev list, however.

Since Xserver 1.7 is now out, and X11R7.5 is at RC1 as of today, it seems an appropriate time to ask what's happened with this promising course of development - we can assume that any linux distro due for release in November or later will include 1.7 (and hence Xinput 2), and it would be lovely if Wine could finally (on such supported systems) resolve most of the mouse capture niggles it has using Xinput 1.

Warren Dumortier · Post by **Warren Dumortier** » Sun Oct 18, 2009 9:41 am

There should be a discussion between Wine developers to implement it as soon
as possible!

Will this version be included in the next Ubuntu release?

2009/10/18 aoanla <[email protected]>

Hello everyone,

I recall, around when XInput 2 was first being discussed as imminent (and,
due to the nature of the X release process, turned out not to be), some
initial work was done on implementing "proper" relative mouse movement using
it.

I can't seem to find any record of it after the first implementation was
thrown out to the dev list, however.

Since Xserver 1.7 is now out, and X11R7.5 is at RC1 as of today, it seems
an appropriate time to ask what's happened with this promising course of
development - we can assume that any linux distro due for release in
November or later will include 1.7 (and hence Xinput 2), and it would be
lovely if Wine could finally (on such supported systems) resolve most of the
mouse capture niggles it has using Xinput 1.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

Thunderbird · Post by **Thunderbird** » Sun Oct 18, 2009 12:57 pm

The xinput2 work focused was a quick implementation to see if the xorg stuff worked fine for us and if we need more. It also served to explore what needs to be changed in Wine to support it. Before xinput2 can be merged into Wine a big part of the input code needs to be rewritten and after that xinput2 can be added but this is a huge amount of work and might take months. Nobody is actively working on it, so hopefully it gets finished before Wine 1.2 but I wouldn't count on it.

James Huk · Post by **James Huk** » Sun Oct 18, 2009 2:21 pm

On Sun, Oct 18, 2009 at 7:57 PM, Thunderbird <[email protected]> wrote:

The xinput2 work focused was a quick implementation to see if the xorg stuff worked fine for us and if we need more. It also served to explore what needs to be changed in Wine to support it. Before xinput2 can be merged into Wine a big part of the input code needs to be rewritten and after that xinput2 can be added but this is a huge amount of work and might take months. Nobody is actively working on it, so hopefully it gets finished before Wine 1.2 but I wouldn't count on it.

Great, but PLEASE leave old code if possible in form of a
compatibility option - I think it should be possible to switch between
both input methods by registry for example

Thunderbird · Post by **Thunderbird** » Sun Oct 18, 2009 3:03 pm

Certainly the old code must stay because only a fraction of the users will have xinput2 and we also need to work on old Xservers and Xservers (e.g. remote X11) without xinput2. This is also one of the things which complicates the design because big chunks need to be rewritten, some stuff needs to be moved to explorer and both the old/new stuff have to work.

aoanla · Post by **aoanla** » Sun Oct 18, 2009 3:38 pm

Thunderbird wrote:The xinput2 work focused was a quick implementation to see if the xorg stuff worked fine for us and if we need more. It also served to explore what needs to be changed in Wine to support it. Before xinput2 can be merged into Wine a big part of the input code needs to be rewritten and after that xinput2 can be added but this is a huge amount of work and might take months. Nobody is actively working on it, so hopefully it gets finished before Wine 1.2 but I wouldn't count on it.

I'd be willing to vote for XInput2 integration to be a blocker for Wine 1.2, actually. It's clearly necessary to properly support DirectInput in the way that a lot of games assume that it is, without hacky workarounds like flaky mouse-warping.

Thunderbird · Post by **Thunderbird** » Sun Oct 18, 2009 4:01 pm

Certainly nobody will say that it is not important but like this there are quite a lot of other areas and we only have a small number of developers. Most people like me who work on Wine are volunteers and work on the things they like. If we fix all issues similar like this we will never get to 1.2. We really need more developers.

aoanla · Post by **aoanla** » Mon Oct 19, 2009 4:11 am

Indeed; there was never any intent to argue that you guys should be working harder (or that you aren't working hard enough).
The initial intent of this thread was more to see if the guy who clearly was interested in XInput 2 stuff was still interested in it, or what happened to him otherwise.

Warren Dumortier · Post by **Warren Dumortier** » Mon Oct 19, 2009 5:32 am

Stupid comment, but why not making a page to seek developers...
There are maybe developers not involved in Wine that would like to help
because they have skills in that component.

2009/10/19 aoanla <[email protected]>

Indeed; there was never any intent to argue that you guys should be working
harder (or that you aren't working hard enough).
The initial intent of this thread was more to see if the guy who clearly
was interested in XInput 2 stuff was still interested in it, or what
happened to him otherwise.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>

Post by **dimesio** » Mon Oct 19, 2009 7:20 am

Warren Dumortier wrote:Stupid comment, but why not making a page to seek developers...
There are maybe developers not involved in Wine that would like to help
because they have skills in that component.

You mean like the big Developers link on the home page with the subtitle "Become a Wine developer" that leads to http://www.winehq.org/devel/ ?

Thunderbird · Post by **Thunderbird** » Mon Oct 19, 2009 7:33 am

Everyone who submits patches to Wine is a Wine developer and everyone can do that

Warren Dumortier · Post by **Warren Dumortier** » Mon Oct 19, 2009 1:45 pm

But i mean making some publicity for developers. Maybe even Windows
developers would be interrested.
A bit a dumb comment, but who knows!

2009/10/19 Thunderbird <[email protected]>

Everyone who submits patches to Wine is a Wine developer and everyone can
do that

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-us ... chment.htm>