On Fri, 29 Apr 2022 14:59:41 GMT, Alexander Scherbatiy <alex...@openjdk.org> wrote:
>> There are sometimes multitouch events detected, when only a single touch >> should be detected under certain conditions. This lead to touch events on >> previous touch positions. >> >> The referenced bug is closed with "won't fix" with the justification it >> would be platform specific. But this is not correct. It affects all Linux >> platforms combined with a touch controller, which sends the touch events in >> an uncommon, but valid(!), order. >> >> We encountered this problem with the touch controller ILI2511 with firmware >> V6000_V1 in the Tianma display TM070JVHG33. This patch fixes the problem. It >> is the same patch attached to above bug report. > > The 8087370 includes > [LinuxStatefulMultiTouchProcessor-fix-for-1.patch](https://bugs.openjdk.java.net/secure/attachment/50236/LinuxStatefulMultiTouchProcessor-fix-for-1.patch) > to fix the first described case: > > 1. Consider you're touching the screen with two fingers, for example > coordinates > of one point is ~100,100 and second point is ~200,200. While still touching > around > the same points some events are reported with one or another point > to be either 100,200 or 200,100. > > Is it reproduced on your system as well? > > It relates to `8282104: Node zoom/rotate flickers on Raspberry Pi with > Touchscreen` with fix #737 which suggests to not take LinuxInput.ABS_X/Y > events into account for non zero slots instead just skipping them for all > slots. Unfortunately, I can't afford time to burrow into the issue again for writing tests at the moment. @AlexanderScherbatiy is there any chance you can provide a test case? ------------- PR Comment: https://git.openjdk.org/jfx/pull/641#issuecomment-1584015830
