Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode is sometimes blurry on multiple displays as does not respect per-monitor DPI settings #27300

Closed
wojciechka opened this issue May 25, 2017 · 1 comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@wojciechka
Copy link

  • VSCode Version: 1.12.2
  • OS Version: Windows Pro 10 x64 creators update (10.0.15603)

Steps to Reproduce:

  1. 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
  2. Log out and log in or restart OS to apply DPI settings completely
  3. 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.

@wojciechka
Copy link
Author

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.

@roblourens roblourens added the *duplicate Issue identified as a duplicate of another issue(s) label May 26, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants