https://bugs.kde.org/show_bug.cgi?id=446654
--- Comment #48 from Roke Julian Lockhart Beedell <4wy78...@rokejulianlockhart.addy.io> --- (In reply to Niccolò Venerandi from comment #46) > > btw, if there's already an option/code to clone an existing panel, why > > can't this Feature Request be implemented in form of automatically > > triggering that "clone" feature when a new monitor is added in case doesn't > > have any panel yet? > > This could be done, but I'm a bit worried about the consequences it might > have. What if the user has multiple panels? Should we always clone *all* > panels from one screen to another? Is that what the user really expects when > connecting to a new monitor? It's certainly not what I would expect. (In reply to Maxim from comment #44) > btw, if there's already an option/code to clone an existing panel, why can't > this Feature Request be implemented in form of automatically triggering that > "clone" feature when a new monitor is added in case doesn't have any panel > yet? Because that's different functionality. This FR is about an automatic visual replication by rendering one configuration to other monitors, whereas your proposal would be to automatically duplicate one configuration to all other monitors. Each configuration would then need to be rendered independently, and presumably `plasmashell` would overwrite the 2nd-to-last modified panels with the modifications performed to the last-modified one? -- You are receiving this mail because: You are watching all bug changes.
