> windows behavior, but currently necessary. The hid->xinput mapping is already non-compliant with the > the proper way to implement xinput would be to access the USB devices > Wine is supposed to mimic Windows' behavior as well as possible. For this to work we need to report an actual > enumeration part, which many (older) games do through a mixture of > up the HID data the other challenge for xinput devices is the > SteamController) provided we want to support this. > this is handling of non-native xinput devices (e.g. > In my opinion, I'm not sure what the best way would be to handle > Let me reply to the start of the thread before diving into the > On 02:45 AM, Roderick Colenbrander wrote: > On Sat, at 10:59 AM, Juan Jose Gonzalez wrote: > On 3/21/16 7:27 PM, Roderick Colenbrander wrote: > On Tue, at 5:35 AM, Aric Stewart wrote: On 3/23/16 12:20 AM, Roderick Colenbrander wrote: Next message: XInput and HID - architecture.Previous message: XInput and HID - architecture.XInput and HID - architecture Aric Stewart aric at
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |