As of Windows 8.1 (and later), Windows applications can support DPI settings per monitor (as opposed to a single system wide DPI setting).

Long story short, to get the best possible experience, applications have to be coded specifically to support this new feature, otherwise blurriness will occur in certain scenarios, as Windows will scale automatically, "The effect is that the window and content size are appropriate for every display, but the scaling introduces blurriness.".

Official doc: https://msdn.microsoft.com/en-us/library/windows/desktop/dn469266(v=vs.85).aspx

There is a good summary here: http://www.anandtech.com/show/7939/scaling-windows-the-dpi-arms-race/5

This has 2 implications:

1) Applications need to support DPI setting per top-level window (as opposed to application wide) <= This is required because top level windows of a single application may appear on separate displays, each one with distinct DPI settings.

2) Applications need to be able to apply a new DPI setting to any top level window at run-time, without restarting <= This happens when a window is moved by the user from one display to another display with a different DPI setting.

Implementation notes:
* Supporting this feature means that every top level windows of Android Studio will have it's own DPI (and scaling factor), so relying on a global scaling factor is not an option anymore.
* This also means that the application needs to support dynamically (i.e. at run time) scaling to a different factor all components of a top level window in response to the WM_DPICHANGED message.
* The two points above make the approach currently implementated in the JBUI class obsolete.

Issue 37061280

Links (6)

Issue metadata