On Fri Jul 10 07:11:36 2026 +0000, Rémi Bernon wrote:
The second commit accumulates unaccelerated inputs like we currently do for accelerated inputs, since dx_unaccel uses wl_fixed type the compositor could send 0.375 for example, and we would treat that as zero. The values are typically integers in my experience, but I think it would be good to ensure that we don't drop any valid inputs. I don't think this is necessary, the raw values should be integer. At most we could have a FIXME in anything has a decimal part just in case. From https://wayland.app/protocols/relative-pointer-unstable-v1
It says:
Note that the non-accelerated delta does not represent 'raw' events as they were read from some device. Pointer motion acceleration is device- and configuration-specific and non-accelerated deltas and accelerated deltas may have the same value on some devices.
It does say that unaccel isn't raw but it's closer to raw than pretending that the accelerated values are also raw. I guess it's probably fine to assume they are integer (since that is typically what happens) but it is better to be safe imo -- https://gitlab.winehq.org/wine/wine/-/merge_requests/11357#note_145364