https://bugs.kde.org/show_bug.cgi?id=447044
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|No good way to manage |No good way to access and
|panels on non-visible |migrate data from
|containments for screens |containments for screens
|that are currently turned |that are currently turned
|off |off
Ever confirmed|0 |1
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFIRMED
--- Comment #4 from Nate Graham <n...@kde.org> ---
(In reply to qlum from comment #2)
> There would be two main reasons outside multi-monitor bugs to want them.
> First to clean up the related configuration files when you know you will not
> connect the monitor again.
Since the configuration data is benign just sitting there on disk, I don't
think this is really a valid use case. You never know, you might use that
screen again! And if it's driving you crazy, you can always edit the config
file by hand.
> Second would be to migrate a panel configuration to a new display layout.
This seems like a more valid use case, because you could have a panel config on
one layout that becomes inaccessible and unable to be moved to a different
layout.
We are currently experimenting with an idea to make layouts bound not to
specific screens, but to the numerical position that a screen occupies in a
multi-screen layout.
So for example when you have two screens, your second screen gets its own
layout, but if you unplug that screen and plug in a totally different screen,
it would get the same layout that the old Screen #2 got. So the layout for
Screen #2 would never become inaccessible as long as you still had two screens.
However this wouldn't help in the case where, say, you had three screens,
decided 2 was enough, but wanted to migrate your setup from screen #3 to Screen
#2. So we would still have a niche use case for this even with the proposed
change. Thankfully this would be satisfied by another piece of in-progress
work: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1136.
> As for the multi monitor issues, I wish I could point at do x and a panel is
> gone, sadly I have not been able to reproduce the issues on demand. It just
> happens somewhat randomly at times, sometimes after boot, sometimes after a
> gaming session disabling all but my main display, saldy nothing more I can
> say that it happens somewhat frequently. On average, I would say every other
> week, but it is fairly random.
I understand. The code for multimonitor stuff is super awful and fragile and
we're currently working on it.
--
You are receiving this mail because:
You are watching all bug changes.
