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

Add pressed()/released()/clicked() signals to Flickable

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Out of scope
    • P3: Somewhat important
    • None
    • None
    • None

    Description

      Flickable consumes press events by necessity in order to determine whether or not the user is flicking it. The basic example in qtvirtualkeyboard.git works around this by adding a MouseArea as a child of the Flickable to intercept click events:

      https://code.qt.io/cgit/qt/qtvirtualkeyboard.git/tree/examples/virtualkeyboard/basic/Basic.qml#n51

      With a clicked() signal, we could simply do:

          Flickable {
              // ...
              onClicked: relieveInputFieldsOfTheirFocus()
          }
      

      Apparently there is an issue that Flickable considers itself pressed when using a touchpad on Mac, so that these new signals would be triggered when flicking in that case, which we don't want. We'd need to ensure that we distinguish between actual clicks and flicking in this case.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            mitch_curtis Mitch Curtis
            mitch_curtis Mitch Curtis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes