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

QObjectPicker::clicked() signal is not emitted immediately if QRenderSettings::renderPolicy is set to OnDemand

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P1: Critical
    • 5.9.0 RC
    • 5.9.0 Beta 3
    • Qt3D
    • Attached example tested on MacOSX (10.10.1) with clang 7.0.2 64bit.
      The archive contains the output of qtdiag.

    • 041529012f7c329d786fcb7190c28afc1477f1c2

    Description

      I'm using the QObjectPicker to select a mesh in a Qt3DWindow with the mouse.
      All works as expected, if I click on the mesh, the signal QObjectPicker::clicked() is sent immediatly.

      But if I set the property QRenderSettings::renderPolicy to OnDemand, then the signal QObjectPicker::clicked() is emitted only when the rendering is done (when something changes, as says the documentation of QRenderSettings::renderPolicy).

      Worst, if I click several times, then each click is "stacked", until the rendering is done. Then the signals QObjectPicker::clicked() is sent serveral times.

      1. launch the attached example
      2. click one or more times on the black rectangle
        EXPECTED: message "Cube clicked" must appears in the console as many times as click on the rectangle.
        ACTUAL: message "Cube clicked" appears in the console as many times as click on the rectangle only if I resize the window.

       

      Attachments

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

        Activity

          People

            lemire_p Paul Lemire
            iohannrabeson Iohann Rabeson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes