https://bugs.kde.org/show_bug.cgi?id=525557
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REPORTED |CONFIRMED CC| |[email protected], | |[email protected], | |[email protected] Ever confirmed|0 |1 Component|Panel |Containment Keywords| |multiscreen --- Comment #1 from Nate Graham <[email protected]> --- I can see how this is a problem for you, yeah. The thing is, being positional is the intended design. It's possible the intended design doesn't fit your use case, in which case we've got some thinking to do. But here are the limitations: 1. Mapping containments to connector IDs doesn't work because they're volatile. 2. Mapping containments to monitor UUIDs doesn't work because are not guaranteed to actually be unique. 3. Even if there was a unique identifier, using it might not do what the user wants. For example, imagine a laptop that floats between multiple setups with different monitors. You'd want the containment in position 2 to appear on both external monitors, no matter which one the laptop was plugged into. So my sense is that the only real way to improve the situation for you would be to: 1. Come up with a truly unique identifier for screens 2. Allow the user to opt into containments to be bound to those identifiers, rather than a fixed position I'm not sure it's possible, TBH. We had virtually endless bugs with the old non-positional system that all went away. Now the only bug reports we get are from folks like you with complex and detailed setups that are not handled by the current design. -- You are receiving this mail because: You are watching all bug changes.
