On Wed, 27 Apr 2022 11:01:46 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 fix #746 for 8282702 also proposes to copy the touch state. The fix makes > it in LinuxStatefulMultiTouchProcessor class. > Do issues 8087370 and 8282702 have the same root? @AlexanderScherbatiy I think both issues address the same problem in quite the same way. However, #746 solves the problem only for LinuxStatefulMultiTouchProcessor. This pull request implements the fix more generally in the TouchPipeline so that other touch processors (e. g. LinuxStatelessMultiTouchProcessor and LinuxSimpleTouchProcessor) can also benefit. ------------- PR: https://git.openjdk.java.net/jfx/pull/641
