c97e58bb61
If a window is positioned with setFramePosition, we reflect that to the platform window via QPlatformWindow::setGeometry(), but with the QWindowPrivate::positionPolicy set to WindowFrameInclusive. On the platform side the position policy is read from QWindowPrivate to determine how to interpret the incoming geometry. When the resulting geometry is applied to the native window, it's reflected through QPlatformWindow::geometry() and reported back via QWSI::handleGeometryChange() as client geometry, ie. without the frame margins. If the platform layer later interprets this geometry in combination with the window's positionPolicy, it will incorrectly position the frame top left at the point of the client geometry's top left. It would make sense to reset the window's positionPolicy at the point of QGuiApplicationPrivate::processGeometryChangeEvent, but doing so might break situations where there's another in flight geometry request. What we can do as a first step is reset the positionPolicy when the platform window is destroyed. This ensures that the next time the platform window is created it will be placed at the same position, even if the initial position was requested via the setFramePosition() API. Change-Id: Ic555f19884ccd68c46421d0fe666717170ba7638 Reviewed-by: Oliver Wolff <oliver.wolff@qt.io> Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io> Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit 11a09a9bd0a7e899a918b078a94c6c3b82240dee) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org> |
||
|---|---|---|
| .. | ||
| image | ||
| itemmodels | ||
| kernel | ||
| math3d | ||
| painting | ||
| platform | ||
| qopengl | ||
| qopenglconfig | ||
| qvulkan | ||
| rhi | ||
| text | ||
| util | ||
| CMakeLists.txt | ||