https://bugs.kde.org/show_bug.cgi?id=460260

Nate Graham <n...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Version Fixed In|                            |5.104
      Latest Commit|                            |https://invent.kde.org/fram
                   |                            |eworks/kconfig/commit/fc46a
                   |                            |2215809abebfdab8ca471c1b27b
                   |                            |65b7ad56
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #20 from Nate Graham <n...@kde.org> ---
Git commit fc46a2215809abebfdab8ca471c1b27b65b7ad56 by Nate Graham.
Committed on 16/02/2023 at 15:21.
Pushed by ngraham into branch 'master'.

Fix multimonitor window size restoration

The size saving and restoring code saves width and height values under a
config key that changes based on the active screens, the name of the
current screen, and the resolution of the current screen. This suffers
from a few issues:
- Due to https://bugreports.qt.io/browse/QTBUG-50788, what counts as the
  current screen is volatile at runtime, and hence data gets saved to
  and read from different config file keys.
- Including the screen resolution of the current screen only makes sense
  for single-screen setups anyway as it's just random data causing
  entropy for multi-screen setups.

Both of these issues contribute to the problem of window size being
restored incorrectly for multi-screen setups.

This commit fixes the issue by no longer including current-screen-based
data in the config file keys for multi-screen setups; just including the
current set of screens is good enough and it's non-volatile within the
scope of what we care about.
FIXED-IN: 5.104

M  +11   -4    src/gui/kwindowconfig.cpp

https://invent.kde.org/frameworks/kconfig/commit/fc46a2215809abebfdab8ca471c1b27b65b7ad56

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to