https://bugs.kde.org/show_bug.cgi?id=489072
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|NOR |HI
--- Comment #5 from David Edmundson <k...@davidedmundson.co.uk> ---
>... as mSurface->oldestEnteredScreen being null is allowed and fine
QPlatformWindow::screen being null is a big surprise. I want to understand
that rather than just lazily add a guard.
The wayland backend always ensures there's a screen as far as Qt is concerned.
If there's no screen added we'll make a placeholder screen.
QGuiApplication:;primaryScreen() should always be valid.
QWindow caches the screen pointer. When a window is added it starts on a
primary screen. Whenever a screen is removed
(QWindowSystemInterface::handleScreenRemoved) we loop through all windows and
assign any windows now not on a screen to the primary screen. If application
code calls QWindow::setScreen(null) it gets put on the primary screen.
--
You are receiving this mail because:
You are watching all bug changes.
