diff options
| author | Liu Heng <liuhenga@uniontech.com> | 2025-08-01 15:58:15 +0800 |
|---|---|---|
| committer | David Edmundson <davidedmundson@kde.org> | 2025-08-04 01:48:28 +0000 |
| commit | 8ac505b29820c09100ff3efd0c2be4f7b5a71d08 (patch) | |
| tree | fb8b5153707806dd78bd2873d5865c372c5184d4 /src/corelib/thread/qthreadpool.cpp | |
| parent | faba9d680652346ea1dcf6dcc4ecbbef1746e601 (diff) | |
wayland: Use availableGeometry() instead of geometry() in screen updates
In QWaylandScreen::updateOutputProperties() and updateXdgOutputProperties(), replace the second geometry() parameter with availableGeometry() when calling QWindowSystemInterface::handleScreenGeometryChange().
Although currently geometry() and availableGeometry() return the same value due to the lack of work area concept in core Wayland protocols, this assumption may not hold in future or custom compositor extensions. Since availableGeometry() is a virtual function, it allows runtime customization and overriding in subclasses.
Using geometry() unconditionally here may hinder future implementations that wish to support distinct available geometry values, such as excluding panels or reserved areas.
Change-Id: I13a17754cc6794502dc1768fd4f96ca990df1fc7
Reviewed-by: David Edmundson <davidedmundson@kde.org>
Diffstat (limited to 'src/corelib/thread/qthreadpool.cpp')
0 files changed, 0 insertions, 0 deletions
