Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Windows] DPI/Scale/Zoom introduce issues

See original GitHub issue

I have 3 monitors 1920x1080. Calling si.displays I get :

{
    "displays": [
        {
            "vendor": "",
            "model": "Default Monitor",
            "main": true,
            "builtin": true,
            "connection": "INTERNAL",
            "resolutionx": 1920,
            "resolutiony": 1200,
            "sizex": 52,
            "sizey": 32,
            "pixeldepth": "32",
            "currentResX": 1920,
            "currentResY": 1200,
            "positionX": 0,
            "positionY": 0
        },
        {
            "vendor": "",
            "model": "Default Monitor",
            "main": false,
            "builtin": false,
            "connection": "DP",
            "resolutionx": 1920,
            "resolutiony": 1200,
            "sizex": 52,
            "sizey": 32,
            "pixeldepth": "32",
            "currentResX": 1920,
            "currentResY": 1200,
            "positionX": 1920,
            "positionY": 0
        },
        {
            "vendor": "",
            "model": "Default Monitor",
            "main": false,
            "builtin": false,
            "connection": "DP",
            "resolutionx": 1920,
            "resolutiony": 1200,
            "sizex": 52,
            "sizey": 32,
            "pixeldepth": "32",
            "currentResX": 1920,
            "currentResY": 1200,
            "positionX": 3840,
            "positionY": 0
        }
    ]
}

which is expected.

But when I change the scale of the 1st monitor to 150% for instance, I get

{
    "displays": [
        {
            "vendor": "",
            "model": "Default Monitor",
            "main": true,
            "builtin": true,
            "connection": "INTERNAL",
            "resolutionx": 1280,
            "resolutiony": 800,
            "sizex": 52,
            "sizey": 32,
            "pixeldepth": "32",
            "currentResX": 1280,
            "currentResY": 800,
            "positionX": 0,
            "positionY": 0
        },
        {
            "vendor": "",
            "model": "Default Monitor",
            "main": false,
            "builtin": false,
            "connection": "DP",
            "resolutionx": 1920,
            "resolutiony": 1200,
            "sizex": 52,
            "sizey": 32,
            "pixeldepth": "32",
            "currentResX": 1920,
            "currentResY": 1200,
            "positionX": 1920,
            "positionY": 0
        },
        {
            "vendor": "",
            "model": "Default Monitor",
            "main": false,
            "builtin": false,
            "connection": "DP",
            "resolutionx": 1920,
            "resolutiony": 1200,
            "sizex": 52,
            "sizey": 32,
            "pixeldepth": "32",
            "currentResX": 1920,
            "currentResY": 1200,
            "positionX": 3840,
            "positionY": 0
        }
    ]
}

The scaling is correct 1920/1280 = 150%. But the current X position of the 2nd monitor is still 1920 not 1280. There is no way to know the 1st monitor has been scaled (original resolution is lost).

Expected behavior The X position of the 2nd monitor must be 1280. Have information which help to detect a monitor is ‘scaled’ and how much.

Environment:

systeminformation package version: 4.22.3
OS: Windows 10.0.17134 Build 17134
Hardware : Dell Latitude 5591/Intel® UHD Graphics 630/Monitor DELL U2410

Issue Analytics

State:
Created 4 years ago
Comments:11 (10 by maintainers)

Top GitHub Comments

1reaction

sebhildebrandtcommented, Oct 9, 2021

@emmkimme … two things:

I guess it is possible to set the positionx for the monitors in scaled environments correctly, will come up with a solution
and for the scaling, not sure if I can add this correctly… need to work on it.

1reaction

sebhildebrandtcommented, Oct 9, 2021

@OmgImAlexis interesting output …

I wonder why wmic path win32_desktopmonitor get /value just reports ONE monitor
also interesting is that powershell Add-Type -AssemblyName System.Windows.Forms; [System.Windows.Forms.Screen]::AllScreens returns an error …

Any ideas? And what is then the output from systeminformation on your machine?

Top Results From Across the Web

Windows scaling issues for high-DPI devices - Microsoft Support

To work around scaling issues, try the following methods: ... Change application properties In Explorer or on the Start menu, right-click the application...

How to Configure Display Scaling on Windows 10 for High ...

Go to the folder where the program is installed, then right-click on the program's icon and select Properties.

Microsoft May Never Fix the High DPI Issues in Windows 10

If the resolution of the display on that PC is high enough, and the physical size of that display is small enough, then...

8 Ways to Fix Any Chrome Scaling and Zoom Issues

4. Change the scaling setting in Windows · Press Windows Key + I to open the Settings app. · Now go to the...

Impact of zoom level/Windows scaling – UpSlide Help & Support

All of these issues can also be caused by the screen resolution. You can access these settings by right-clicking on the desktop and...