Thanks all for the info and insight.<br><br>On 21 March 2011 07:48, Stefan Dösinger <span dir="ltr"><<a href="mailto:stefandoesinger@gmx.at">stefandoesinger@gmx.at</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sunday 20 March 2011 21:46:34 Austin English wrote:<br>
> > There are some patches still around (would have to look them up) and<br>
> > they work.<br>
</div><warn reason="clueless"><br>
I think the main problem with implementing xinput.dll isn't xinput itself, it<br>
is the lack of a proper joystick infrastructure in wine. Currently dinput.dll<br>
reads the /dev/js* devices directly, but preferably joystick input should be<br>
done over the X server and winex11.drv. This needs some tricky adjustments,<br>
winex11.drv isn't a place where you can just add some hacky code and hope<br>
Alexandre doesn't notice.<br>
</warn><br></blockquote><div><br>If dinput is currently implemented this way, what's the problem with implementing xinput in the same way, at least for now? It can always be refactored later if needed. Is this the only reason why the patches didn't make it in before?<br>
</div></div><br>