| Summary: | Screen settings panel: Presence of available inactive screens is hard to determine | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Gerion <gerion.entrup> |
| Component: | kcm_kscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | kde, kleagg, nate, plasma-bugs |
| Priority: | NOR | Keywords: | usability |
| Version: | 5.26.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | monitor.png | ||
|
Description
Gerion
2019-11-04 09:40:21 UTC
Please try to focus on what the issue itself is, rather than what you want the solution to be. Which specific part of the current UI is misleading? The current UI consists of a panel (upper half), where the actual screen configuration is shown and the lower half, where detailed screen settings are listed. I want that the upper half panel also shows the deactivated (but recognized) screens in gray. Exactly as it was the behaviour before 5.17. >Please try to focus on what the issue itself is, rather than what you want the solution to be.
What is the issue caused by not showing the disabled screens in the arrangement area.
Leaving as needsinfo.
Created attachment 123739 [details] monitor.png (In reply to David Edmundson from comment #3) > What is the issue caused by not showing the disabled screens in the > arrangement area. Users are unable to see that other monitors are present (recognized by the system) or are not able to select it in a fast way. I marked the visual indicators for other monitors in the screenshot. Previewing the inactive display is a much bigger indicator that other screens are present. It's interesting that you had 3 screens. The case of going between 1 and 2 screens is more obvious because a whole combo box and page indicator appear, but 2 -> 3 wouldn't have that. Reopening for UX discussion on what we do next. Perhaps we could show disabled screens in the visualization with low opacity and the text "Disabled" appended to its label. But I think the greater problem is that screens show up as disabled far too often in the new KCM. If you as the user haven't specifically disabled a screen, it shouldn't be disabled. When you plug in a screen, it should be enabled by default (if you didn't want it enabled, you wouldn't have plugged it in). >If you as the user haven't specifically disabled a screen, it shouldn't be disabled. When you plug in a screen, it should be enabled by default (if you didn't want it enabled, you wouldn't have plugged it in).
We should restore the state we were last in when we had that set of monitors plugged in. That's all within the KDED rather than the KCM and AFAIK that is completely unchanged.
(In reply to David Edmundson from comment #7) > >If you as the user haven't specifically disabled a screen, it shouldn't be disabled. When you plug in a screen, it should be enabled by default (if you didn't want it enabled, you wouldn't have plugged it in). > > We should restore the state we were last in when we had that set of monitors > plugged in. That's all within the KDED rather than the KCM and AFAIK that is > completely unchanged. Yes, this is the behaviour I experienced. Especially on my laptop, which I have connected to several beamers/TVs/screens, the last configuration for that specific device is restored. Afaik, also a quick setup is shown, when a new screen (never connected before) is plugged it. However, my concern is about a setup where a screen is not permanently active but activated only when needed (one of my screens for example is a TV that is off and deactivated most of the times). *** Bug 416976 has been marked as a duplicate of this bug. *** |