https://bugs.kde.org/show_bug.cgi?id=493195
--- Comment #7 from Maxim <maxim.kukush...@gmail.com> --- (In reply to Nate Graham from comment #6) > Manually, though. I don't think we're going to be doing any automatic panel > cloning, as the behavior would be challenging to predict: > 1. What about monitors that, due to their own hardware issues, get detected > as "newly connected" every time? > 2. What about setups with more than one panel on the original monitor? > 3. What about setups where a single panel on the original monitor would not > fit or make sense on a newly connected monitor (e.g. very wide bottom panel > on monitor 1, and you connect a new portrait-orientation monitor 2? > > For these reasons, there are just too many edge cases, and panel cloning is > going to have to be a manual thing. Hi Nate, please see my comment in the original feature request: https://bugs.kde.org/show_bug.cgi?id=446654#c47 My suggestion is to always ask the user. I.e., let the user set whether to copy or not some panel to the new monitor. This can be an attribute of the panel and can be False by default. If the user intentionally sets the flag, they agree there can be side effects. In many cases it will just work, however in the those edge cases the users will expect this and maybe temporarily unset the flag. Also, if the copied panel is too wide, the user can super quickly delete it. This also solves the question how many panels to copy - specifically those that the user has requested to copy. As I mentioned there the algorithm can also check if the new monitor already has any panels. If there're no panels yet, it looks like the target case for copying the panels. If the monitor already has any panels - big change the user has already connected it before and already done some adjustments. (this behavior just needs to be indicated under some question mark next to the setting) -- You are receiving this mail because: You are watching all bug changes.
