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

Gauthier <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #6 from Gauthier <[email protected]> ---
I experience the same issue.

I have one large external monitor + laptop screen. On X11 the primary display
is my external monitor where I have two panels and 4 stcky notes (the desktop
is in "Desktop" mode).

When login into Wayland all panels *and widgets* appear on the "wrong" screen
(i.e. on the laptop screen).

There is no way to move it all back to the other screen easily. I can move it
all back manually, through it is tedious, then everything works alright. But
then, either: 

- if I unplug my external screen: I got the panels back but no widgets (sticky
notes are gone, well in fact they stay in the "2nd screen").

- if I go back to X11, everything is moved in the non primary screen (and if no
other screen is plugged in, it looks like it's all gone, it's only until I plug
another screen that can see the widget and move them back manually to the
primary screen)

I read on a reddit thread from a KDE contributor that the reasoning behind
removing the concept of primary screen on wayland is that it only deals with
where panels are positioned but that it confused people because people thought
it was about window placement. So the concept was removed altogether. I don't
know if this is still where thoughts are but this "seems" wrong to me in two
ways (IMHO):

- Primary screen deals with panels AND widgets. It basically allows a
per-screen set-up and to switch that set-up between screens in tow clicks (tick
primary screen, press apply). Genius if you ask me! 
Not having that makes very tedious to re-setup everything each time you have a
new screen config (e.g. plug into an unknown screen, add a 3rd screen, etc.)

- That it is confused with the Active Display should be addressed with better
UI, not by removing an entirely different function that happens to have a
similar sounding name. Now I admit that unless specified otherwise in the
Window Management settings, it seems to make sense for windows to open on the
primary screen (i.e. for the Active Display setting to follow the Primary
Screen setting by default, whereas the behaviour currently  is a bit erratic).
This would which partially solved that issue and if then users want a more
elaborated behaviour, they look for it in Window Management settings, which
seems consistant.

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

Reply via email to