Wine Joysticks, seeking a plan

[Aric Stewart]

On 4/16/15 2:12 PM, Ken Thomases wrote:
> On Apr 16, 2015, at 9:46 AM, Andrew Eikum <aeikum at codeweavers.com> wrote:
> 
>> On Thu, Apr 16, 2015 at 08:11:39AM -0500, Aric Stewart wrote:
>>> Now completely unresearched but it may be possible to make a single
>>> joystick driver, maybe replacing winejoystick.drv that would build
>>> only the platform code that is relevant.
>>
>> This makes sense to me, and is how dinput already works. Make some
>> sane API for it and build dinput/winmm/xinput on top of that.
> 
> Makes sense to me, too.
> 
> -Ken
> 
Thanks to the great leads that Vincent gave me about Raw Input and such I ended up on a path reading about the HID minidrivers and the whole HID class.

I bounced the idea that the Joystick support should be in HID and Alexandre seemed warm to the idea. So I will do work to implement and update our hid.dll to see about putting joystick code in there.

Then, all the other joystick areas can be build off of the HID code.  It is already clearly stated in the HID documentation that dinput is a client of the HID code. 

The main trick is going to see if all the special functionality (such as forcefeedback or rumble) has a path through HID or not.

-aric