https://bugs.winehq.org/show_bug.cgi?id=42631
--- Comment #58 from Henri Verbeet hverbeet@gmail.com --- (In reply to Jordan Galby from comment #57)
Created attachment 62161 [details] Fix sub pixel raw motion v3
I fixed it to C99 comments (sorry), and tweaked them to describe a bit more "why" than "how". I guess it would be wiser to consider it as a POC rather than a "submittable fix" for now. For example:
- I'm wondering if there could be a better place for `double accum;` ?
Putting it in struct x11drv_valuator_data doesn't seem wrong to me.
- should `accum` be initialized to `0` or the current pixel fraction of the
absolute position ?
You could probably make a good argument for using the current fraction. I'm not sure whether it would really matter in practice though.
- is there a windows API that can handle sub-pixel mouse motion ? (or mouse
dpi ?)
Rawinput (WM_INPUT) is supposed to report unscaled/unfiltered values, so wouldn't need to report fractional values. I'm not aware of any API that reports fractional values on Windows. Ultimately, I think mouse input should go through the HID layer, but I wouldn't expect that to happen very soon.