https://bugs.kde.org/show_bug.cgi?id=497100
Grant Gryczan <grantgryc...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |grantgryc...@gmail.com
--- Comment #3 from Grant Gryczan <grantgryc...@gmail.com> ---
As a proponent of https://bugs.kde.org/show_bug.cgi?id=446654, I strongly
disagree with this suggestion (though perhaps out of ignorance of its
purpose?). I would expect the purpose of automatically cloning to be to keep
them in sync between different monitors. If that's not possible, it would be
superfluous and potentially misleading to only initially clone automatically
but not automatically clone upon further changes to the original panel. Users
may expect they will remain in sync.
You could solve this by somehow adding extra clarification to this option, but
I don't understand the benefit of it being automatic if the cloned
configuration won't also automatically remain in sync. If users have to create
the initial clone manually, then it's much more natural an understanding that
it won't remain in sync in the future, and they'll have to clone manually again
to keep it in sync.
Keeping them in sync will require cloning manually down the line either way, so
forcing users to do it manually to begin with makes it clear what they'll have
to do, and how to do it, in the future.
It's generally very rare you plug in a new monitor, so in the vast majority of
cases I would expect it to be easier & more intuitive to simply clone it once
or twice than to find and check a box that does so automatically (and
understand its drawbacks). What's the value add? I must be misinterpreting the
point if it isn't to try to maintain the same panel on multiple monitors.
--
You are receiving this mail because:
You are watching all bug changes.
