3 Feb
2020
3 Feb
'20
10:09 a.m.
Hi Ziqing, Thanks for having a look at that issue. We still need however the non-raw values to be send, when RawMotion events are translated to normal messages for instance. It may use raw values only for the WM_INPUT messages. This requires several other changes to be implemented correctly, and there're staging patch series trying to implement that: user32-rawinput-mouse, user32-rawinput-nolegacy, user32-rawinput-mouse-experimental. I've tried to upstream the first patches of th series before the code freeze, but they didn't get accepted. I'll try again at some point. Cheers, -- Rémi Bernon <rbernon(a)codeweavers.com>