https://bugs.kde.org/show_bug.cgi?id=377808
Marco Martin <notm...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |https://commits.kde.org/pla
| |sma-workspace/e0a8df2910fa2
| |72f5ed5913ea38b578f5c7145d0
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from Marco Martin <notm...@gmail.com> ---
Git commit e0a8df2910fa272f5ed5913ea38b578f5c7145d0 by Marco Martin.
Committed on 07/04/2017 at 10:14.
Pushed by mart into branch 'master'.
Correctly handle when a new primary screen displaces the old
Summary:
this is for the following setup:
the primary screen is at position 0,0 and gets disconnected.
the other screen will be moved at 0,0 and becomes primary
the screen is reconnected, the events arrive in the followin order:
1) a new screen gets added, at 0,0 position
(not primary yet, it may be markedredundant)
2) the screen becomes primary, both screens still at 0,0
3) the old screen gets moved out of the way
in the end result none of the two need to be redundant.
adding the old one in the redundant list, will cause reconsideroutputs
to consider it and create a view for it.
Test Plan:
added and removed sevaral times a primary screen at 0,0
also tried other positions of screens to check it doesn't make regressions
Reviewers: #plasma, sebas, subdiff, broulik
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D5323
M +15 -6 shell/shellcorona.cpp
https://commits.kde.org/plasma-workspace/e0a8df2910fa272f5ed5913ea38b578f5c7145d0
--
You are receiving this mail because:
You are watching all bug changes.
