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

S. Bryant <st...@bawue.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |st...@bawue.de

--- Comment #8 from S. Bryant <st...@bawue.de> ---
I'm using Plasma 5.6.2 on OpenSUSE Leap, and the problem is very much still
there.

When I connect my external screen to the laptop, the panel from the laptop
screen may get moved to the external screen (or moved back if it was on the
external screen).  The panel on the external screen doesn't get moved.

Connecting/disconnecting the external screen prior to X starting results in the
same behaviour as doing so after logging in.

Moving a panel to a specific display/position seemed to help for the remainder
of that session, but the behavour reverted at the next login.

Disconnecting the external screen leaves the panels where they are.  While this
bug's problem description could be counted as solved, the underlying issue is
not.

This problem was never correctly addressed in the previous generation of the
software, as there are two opposing use cases:
1. having a panel that always remain visible, and automatically changes screen
to do so (and returns to the user's preferred screen when it becomes available
again).  This is probably what a user expects when a single panel is in use;
Windows also works like this.
2. having panels tied to specific screens, and being unreachable if that
particular screen is not connected.

My recommendations:
On screen disconnect, there should be a check that at least one panel remains
visible - if not, the first panel should be moved (but the lastScreen setting
should not be altered).
On screen connect, each panel should be moved to its 'lastScreen' if there is
no panel already at that position on that screen.
The lastScreen setting should only be updated when a panel is created or when
the user explicitly moves the panel to a different screen.  (Not sure if this
is currently the case.)

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

Reply via email to