Bug 459744 - Represent mirrored displays in a way other than fully overlapping them, which is confusing
Summary: Represent mirrored displays in a way other than fully overlapping them, which...
Status: CONFIRMED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (show other bugs)
Version: 5.25.5
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords: usability
: 470674 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-09-27 15:51 UTC by postix
Modified: 2023-06-09 21:05 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot: How many screens are active? (18.17 KB, image/png)
2022-09-27 15:51 UTC, postix
Details
Mockup: The red screen is fully covered by the selected blue screen (30.12 KB, image/png)
2022-09-27 15:51 UTC, postix
Details

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2022-09-27 15:51:13 UTC
Created attachment 152460 [details]
Screenshot: How many screens are active?

SUMMARY

In kscreen screens can dragged and arranged in a way that they partially or fully overlap. In this case part or all of the screens, which are not selected, may be hidden by the selected screen. Please see screenshot.

It'd be therefore useful, if the non-selected screens were drawn e.g. in a different color and their outline would be visible, even if covered by another screen. Please see the mockup.
Comment 1 postix 2022-09-27 15:51:50 UTC
Created attachment 152461 [details]
Mockup: The red screen is fully covered by the selected blue screen
Comment 2 Nate Graham 2022-09-28 17:09:42 UTC
I think it would make more sense to prevent full overlaps. This isn't a logical physical screen configuration; nobody would position a small screen directly behind a large one such that the small one can't be seen.
Comment 3 Nate Graham 2023-06-05 18:26:43 UTC
*** Bug 470674 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2023-06-09 21:05:48 UTC
*** Bug 470674 has been marked as a duplicate of this bug. ***