D5323: Correctly handle when a new primary screen displaces the old

[Marco Martin]

mart created this revision.
Restricted Application added a project: Plasma.
Restricted Application added a subscriber: plasma-devel.

REVISION 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

REPOSITORY
  R120 Plasma Workspace

BRANCH
  phab/screenDance

REVISION DETAIL
  https://phabricator.kde.org/D5323

AFFECTED FILES
  shell/shellcorona.cpp

To: mart, #plasma, broulik, sebas
Cc: plasma-devel, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20170406/e1fe3381/attachment.html>