Reorder some function calls in X11Window::updateServerGeometry()
The main motivation is to improve code aesthetics. The relative order in which various window properties are configured shouldn't matter.
This commit is contained in:
parent
5d03d58dc1
commit
8256f8e14c
1 changed files with 1 additions and 1 deletions
|
@ -4385,7 +4385,6 @@ void X11Window::updateServerGeometry()
|
|||
const QRectF clientRect = m_clientGeometry.translated(-m_bufferGeometry.topLeft());
|
||||
|
||||
if (oldBufferGeometry.size() != m_bufferGeometry.size() || oldClientRect != clientRect) {
|
||||
updateInputWindow();
|
||||
// If the client is being interactively resized, then the frame window, the wrapper window,
|
||||
// and the client window have correct geometry at this point, so we don't have to configure
|
||||
// them again.
|
||||
|
@ -4404,6 +4403,7 @@ void X11Window::updateServerGeometry()
|
|||
sendSyntheticConfigureNotify();
|
||||
}
|
||||
updateShape();
|
||||
updateInputWindow();
|
||||
} else {
|
||||
m_frame.move(m_bufferGeometry.topLeft());
|
||||
sendSyntheticConfigureNotify();
|
||||
|
|
Loading…
Reference in a new issue