Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-61144

Taps don't occur for Buttons in ListView with pressDelay set

    XMLWordPrintable

Details

    • 8bdf33051aa679db1f060314c6ccab1cb9a77a7a

    Description

      Upgraded to Qt 5.9 from 5.8. All my ListViews have a pressDelay and onClick never happens for ItemDelegates. This only happens on Android an not PC (iOS not tried).

      Removing pressDelay "fixes" the problem.

      Can get buttons to click when pressDelay is present if I press with 2 fingers at the same time.

      Suspect the new multi-touch support for Buttons is the problem.

      Is there a way to disable multi-touch support? I don't need it.

      Attachments

        1. QtQuickMaterialPressDelay.7z
          2.32 MB
          Sandro
        2. simpler.qml
          3 kB
          Shawn Rutledge

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-65823 tst_TouchMouse::buttonOnDelayedPressFlickable() is flaky on Win7/mingw

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Reported

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-69059 [Regression] Fix for QTBUG-61144 reverted in 5.10 and 5.11

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-85607 Flickable delayed-press functionality must resend the same kind of press

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Activity

            People

              srutledg Shawn Rutledge
              obsiv OBsIV
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: