Skip to content

InternalWindowEventFilter: Also track pressed ids for touch points != 0

Aleix Pol Gonzalez requested to merge work/fix-internaltouch into master

So far we were only tracking the first touch point, meaning that if 2 touch points were applied to the internal window and removed one, the second's events would then be sent to Wayland, which would assert since it didn't know it had been pressed in the first place.

This fixes InternalWindowTest::testTouch

Merge request reports