16 Nov
2022
16 Nov
'22
1:15 p.m.
Okay, but this is then only hiding the problem, that kind of error should really never happen as it's not something sent by the controller but instead the value of `RIM_TYPE*` constant. All the possible values are normally handled already (`RIM_TYPEMOUSE`, `RIM_TYPEKEYBOARD`, `RIM_TYPEHID`). I believe we are the ones settings these types and if there's an unexpected type it is that something is going wrong elsewhere and upstream in the HID / input stack, that needs to be fixed. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1364#note_16012