https://bugs.kde.org/show_bug.cgi?id=459328
--- Comment #13 from Yoann Laissus <yoann.lais...@gmail.com> ---
(In reply to David Edmundson from comment #11)
> ok, I have a new theory. Sorry to mess you about but it's easier as you can
> reproduce.
>
> Can you change pointer_input.cpp
>
> static bool screenContainsPos(const QPointF &pos)
>
> - if (output->geometry().contains(pos.toPoint())) {
> + if (output->geometry().contains(QPoint(std::floor(pos.x()),
> std::floor(pos.y())))) {
>
> I'm rounding a point during the check, but if our mouse ends up at -0.4 due
> to some acceleration that would incorrect say we're on screen, not
> auto-correct but then pass a value not valid to our surfaces
Your new theory is totally right, the problem is gone !
Do you want me to add some debug messages to display the pos values if you want
to be sure ?
--
You are receiving this mail because:
You are watching all bug changes.
