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

QWidget receives two resizeEvent's before its first paintEvent

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P3: Somewhat important
    • 5.4.0
    • 5.0.2, 5.1.0
    • Widgets: Widgets and Dialogs
    • None

    Description

      We get one resizeEvent from QWidget's internal sendPendingMoveAndResizeEvents function and one from QGuiApplication::processExposeEvent(). The second one is sent because we guarantee one resizeEvent prior to any expose event in QWindow.

      The test previously passed because we did not allow the event loop to run and the processing of the expose event didn't happen until the test had completed. Any stand alone usecase with a real widget, would have proven the error, however.

      I will update the tst_qwidget::resizeEvent() with a couple of QTest::qWaitForWindowExposed() so that the error becomes visible in the test. The test is marked as QSKIP until the problem is resolved.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-32590 two move events per move call, one in subsequent message loop

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

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-38768 When a widget is programatically resized then it will trigger a spontaneous event even though the event did not originate from the system

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

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-39611 Regression/Windows: QWizard buttons wrongly positioned on branch 5.3 after merge from stable (5.3.0 release tags)

          • 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

              jolind Jorgen Lind
              sletta Gunnar Sletta
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: