Details
-
Bug
-
Resolution: Done
-
P3: Somewhat important
-
5.0.2, 5.1.0
-
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
-
QTBUG-32590 two move events per move call, one in subsequent message loop
- Closed
-
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
- Closed
- resulted in
-
QTBUG-39611 Regression/Windows: QWizard buttons wrongly positioned on branch 5.3 after merge from stable (5.3.0 release tags)
- Closed
For Gerrit Dashboard: QTBUG-30744 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
54063,10 | Fix windows expose logic | stable | qt/qtbase | Status: MERGED | +2 | 0 |
86224,3 | Suppress move/resize events if they are the result of call to move()/resize(). | stable | qt/qtbase | Status: MERGED | +2 | 0 |
97822,17 | Fix too many resizes and move events for native widgets | 5.4 | qt/qtbase | Status: MERGED | +2 | 0 |
98851,1 | Fix too many resizes and move events for native widgets | 5.4.0 | qt/qtbase | Status: ABANDONED | 0 | 0 |