Bug 493309

Summary: Make layout switcher desktop-aware
Product: [Plasma] KScreen Reporter: gudvinr+kde
Component: OSD and Plasma appletAssignee: kscreen-bugs-null <kscreen-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 6.1.90   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description gudvinr+kde 2024-09-18 07:04:25 UTC
SUMMARY

Currently, display layout is laptop-centric and is not aware of actual display "residence".

If you have a desktop PC with 1+N monitors. Then, in OSD you'll see "Switch to external screen" and "Switch to laptop screen". But from a desktop perspective ALL monitors are external and no laptop screens exist.

If "external" monitor means "non-primary", you can also have not 2, but 3 outputs connected. If one of them a TV, that will be "external" by residence and on-desk monitors both would be "primary".

So, this makes OSD and layout switcher almost useless for non-laptop use-cases.

Some of the use-cases not covered by custom configuration:
- on a laptop, you can't "extend to the top" if your laptop below your external monitor
- on a desktop, you can't have 2 monitors available most of the time and switch to TV from time to time
- on both, with more than 2 monitors you can't configure arrangement

This can be solved by:
- custom layout manager where you define layouts and then switch between them
  - this layout manager can also include some pre-defined dynamic layouts (e.g. depending on laptop/desktop, number of monitors)
- adding display role (instead of just marking as primary) to display manager so layout switcher will know that if you have 3 monitors, "that one" is actually presentation display
  - this should be easier to use since you don't need no additional KCM


Operating System: Arch Linux 
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2
Kernel Version: 6.11.0 (64-bit)
Graphics Platform: X11
Comment 1 Nate Graham 2024-09-18 17:52:21 UTC

*** This bug has been marked as a duplicate of bug 445553 ***