On 04.07.2015 0:12, Nathan Schulte wrote:
It looks like what I was was seeing was "Wine drivers," (winejoystick.drv, for winmm's joystick bits, and DirectInput's joystick bits). Should I follow that route, or should I plumb this through wineserver, like the rawinput keyboard and mouse? Why are those plumbed through wineserver? Are they shared resources, and if so, why doesn't that matter for winmm and DirectInput?
I'm thinking this should be fairly easy to get working, by enumerating the rawhid devices and just piping the data through. I'm not sure how well the native hid.dll will work though; can anyone comment?
I don't know if it will work at all, but Aric already started to work on this area, see http://source.winehq.org/git/wine.git/history/HEAD:/dlls/hid. I think the idea is to unify hid device access logic, and move it to a single place that could contain plarform-specific bits still offering same interface to clients.
Any help is welcome, as it means my patches are more likely to make it upstream and benefit others. I'm wondering if there's an architecture diagram/doc somewhere to help me understand how the system works.
CC'ing Aric, to make sure he doesn't miss this.
Thanks,
-- Nate