You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS Version: Windows Pro 10 x64 creators update (10.0.15603)
Steps to Reproduce:
Set up environment with two monitors - primary being 100% DPI scaling and second being higher DPI (i.e. 200%) - a sample setup is HiDPI laptop (such as all Surface devices) with external monitor, where external monitor is the primary display device
Log out and log in or restart OS to apply DPI settings completely
Run vscode move it to the secondary screen with >100% DPI settings
At this point vscode window is scaled up.
It is worth noting that if the primary screen has 200% DPI (i.e. if Surface built-in screen is the primary display, or was primary display at the time the user has logged in), then vscode is not blurry - but then it is downscaled when moving it to the primary monitor.
I believe this is because vscode windows are set to use PROCESS_SYSTEM_DPI_AWARE setting - which makes it use the DPI setting of the primary monitor, not the display it is currently at.
As vscode uses electron, which in turn uses webkit, it should be possible to use PROCESS_PER_MONITOR_DPI_AWARE setting - since chrome does support it properly for quite a while - chrome windows scale properly to each monitor's DPI settings.
The text was updated successfully, but these errors were encountered:
I just realized this is probably a duplicate of #6196
I have also just downloaded electron 1.6.10 and that version seems to be using per-display DPI settings, so I am hoping that updating electron should resolve the problem.
Steps to Reproduce:
At this point vscode window is scaled up.
It is worth noting that if the primary screen has 200% DPI (i.e. if Surface built-in screen is the primary display, or was primary display at the time the user has logged in), then vscode is not blurry - but then it is downscaled when moving it to the primary monitor.
I believe this is because vscode windows are set to use
PROCESS_SYSTEM_DPI_AWARE
setting - which makes it use the DPI setting of the primary monitor, not the display it is currently at.As vscode uses electron, which in turn uses webkit, it should be possible to use
PROCESS_PER_MONITOR_DPI_AWARE
setting - since chrome does support it properly for quite a while - chrome windows scale properly to each monitor's DPI settings.The text was updated successfully, but these errors were encountered: