yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

outputconfigurationstore: restore comment lost in migration from KScreen

Browse source 
This comment is important to explain the underlying reason *why* we have
different target DPIs for different device types.
This commit is contained in:
Nate Graham 2023-06-20 23:59:36 +02:00
parent 7872e7cb22
commit 3ca2870deb
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
src/outputconfigurationstore.cpp
View file

@ -118,6 +118,13 @@ double OutputConfigurationStore::chooseScale(Output *output, OutputMode *mode) c
double OutputConfigurationStore::targetDpi(Output *output) const double OutputConfigurationStore::targetDpi(Output *output) const
{ {
/* The eye's ability to perceive detail diminishes with distance, so objects
* that are closer can be smaller and their details remain equally
* distinguishable. As a result, each device type has its own ideal physical
* size of items on its screen based on how close the user's eyes are
* expected to be from it on average, and its target DPI value needs to be
* changed accordingly.
*/
const auto devices = input()->devices(); const auto devices = input()->devices();
const bool hasLaptopLid = std::any_of(devices.begin(), devices.end(), [](const auto &device) { const bool hasLaptopLid = std::any_of(devices.begin(), devices.end(), [](const auto &device) {
return device->isLidSwitch(); return device->isLidSwitch();