KScreen merge requestshttps://invent.kde.org/plasma/kscreen/-/merge_requests2024-02-27T17:46:07Zhttps://invent.kde.org/plasma/kscreen/-/merge_requests/289kcm: expose checkbox for using the display-provided color profile2024-02-27T17:46:07ZXaver Huglkcm: expose checkbox for using the display-provided color profileThis makes it easier for people without a colorimeter to get closer-to-correct
colors
Depends on https://invent.kde.org/libraries/plasma-wayland-protocols/-/merge_requests/72, https://invent.kde.org/plasma/libkscreen/-/merge_requests/18...This makes it easier for people without a colorimeter to get closer-to-correct
colors
Depends on https://invent.kde.org/libraries/plasma-wayland-protocols/-/merge_requests/72, https://invent.kde.org/plasma/libkscreen/-/merge_requests/184 and https://invent.kde.org/plasma/kwin/-/merge_requests/53086.1https://invent.kde.org/plasma/kscreen/-/merge_requests/152kded: refine initial best scale calculation2022-11-28T23:13:35ZNate Grahamkded: refine initial best scale calculationRight now the "best scale" calculation returns 2.0 or 1.0 based on a
screen's DPI and whether it has 1440 or more vertical pixels. This
works but its fairly basic algorithm misses many screens that would
benefit from some scaling.
In th...Right now the "best scale" calculation returns 2.0 or 1.0 based on a
screen's DPI and whether it has 1440 or more vertical pixels. This
works but its fairly basic algorithm misses many screens that would
benefit from some scaling.
In the messy world we live in, many people have screens with fewer
physical pixels than that, and would benefit from scaling. Biological
factors in how eyes work cause a screen's ideal scale factor to be
based on the physical size of items on screen, which is a function of
its distance from the user's eyes and its pixel density. If we know
these, we can compute an appropriate scale factor for it.
Unfortunately we can't know how far away the screen is from the user's
eyes. As a result, we have to guesstimate based on what type of device
it is plus common sense; people tend to use smaller screens closer to
their faces. For example, if we know a screen is a built-in laptop
screen, its ideal scale factor is slightly smaller than if it were a
small desktop screen.
Accordingly, this commit introduces a new calculation that does away
with the pixel size limit and attempts to compute an ideal scale based
on a screen's device type and DPI. Computed scale factors are rounded
to the nearest 25%.
Implements/fixes https://phabricator.kde.org/T13158
FIXED-IN: 5.27
@teams/usability @ratijas @davidedmundson
## Test plan
1. Apply the MR and compile
2. Move aside `~/.local/share/kscreen/`
3. Reboot and see if the auto-chosen scale for your hardware feels okay5.27https://invent.kde.org/plasma/kscreen/-/merge_requests/115Use XWayland client scaling by default2022-09-10T18:14:37ZNate GrahamUse XWayland client scaling by defaultWe discussed potentially turning this on for Plasma 5.26, but wanted to
do more testing first. I as well as other KDE contributors have been
running with it on for the past month with seemingly no drama. Seems
like it's safe enough to tu...We discussed potentially turning this on for Plasma 5.26, but wanted to
do more testing first. I as well as other KDE contributors have been
running with it on for the past month with seemingly no drama. Seems
like it's safe enough to turn on by default now.
This commit slightly re-arranges the KCM's UI so that the radio button
corresponding to the default setting remains on top.
cc @vladz @zamundaaa @davidedmundson @apol5.26Nate GrahamNate Grahamhttps://invent.kde.org/plasma/kscreen/-/merge_requests/101kcm: Expose the new XwaylandClientsScale setting on the UI2022-06-15T10:56:35ZAleix Pol Gonzalezkcm: Expose the new XwaylandClientsScale setting on the UI5.26https://invent.kde.org/plasma/kscreen/-/merge_requests/35feat(kcm): add revert timer2021-09-05T12:06:59ZChris Rizzitellofeat(kcm): add revert timerUpdated Version of [Feature Add Revert Timer](https://invent.kde.org/plasma/kscreen/-/merge_requests/1) with these additional Changes
- Exposes A [bug](https://bugs.kde.org/show_bug.cgi?id=441572) in system settings that after hitting a...Updated Version of [Feature Add Revert Timer](https://invent.kde.org/plasma/kscreen/-/merge_requests/1) with these additional Changes
- Exposes A [bug](https://bugs.kde.org/show_bug.cgi?id=441572) in system settings that after hitting apply a kcm loses activeFocus.
- Can not force keyboard focus to the revert dialog
- Action Shortcuts function correctly.
- Rebased, Cleaned Commits.
- New private method `bool ConfigHelper::checkSaveandTestCommon(bool isSaveCheck)`
- used as a common back end for `ConfigHelper::checkNeedsSave` and `ConfigHelper::shouldTestNewSettings`
- Use "Configuration" consistently
- Cleaned up some [Zixing Liu](https://invent.kde.org/liushuyu) 's code
- Use function OnFoo style Connection Type
- Addressed the open threads
- Do not prompt to keep configuration if the scale changed on X11.
- Do not prompt when changing the way the config is stored
- Use Kirigami OverlaySheet for a cleaner dialog
- <img src="/uploads/b2c77573e1453a3fd844f70ceeff4ef3/2021-08-26_1.png" width=50%>
- Use Enter and Escape as action shortcuts along with Alt+K / Alt+R5.23Chris RizzitelloChris Rizzitellohttps://invent.kde.org/plasma/kscreen/-/merge_requests/1feat(kcm): add revert timer2021-08-22T13:50:46ZZixing Liufeat(kcm): add revert timer## Description
Add a revert timer and an option for the user to revert the settings when they accidentally messed up the settings and unable to see the screen.
## Screenshots
![image](/uploads/43e1bf68915c58df3c896e3875639a97/image.pn...## Description
Add a revert timer and an option for the user to revert the settings when they accidentally messed up the settings and unable to see the screen.
## Screenshots
![image](/uploads/43e1bf68915c58df3c896e3875639a97/image.png)
![image](/uploads/de207be8d8eec7beb2e9152f7084f6b5/image.png)
Migrated from https://phabricator.kde.org/D255395.23