<AWT Dev>  RFR for JDK-8199627: Use "Per-Monitor V2" High DPI awareness for Windows 10 v1703
Magnus Ihse Bursie
magnus.ihse.bursie at oracle.com
Mon Apr 16 12:26:52 UTC 2018
Since this patch, I'm getting lots of warnings on Windows:
: manifest authoring warning 81010002: Unrecognized Element
"dpiAwareness" in namespace
Seems this element is not universally recognized. Does it even work as
Do you have any suggestion on how to address this issue?
On 2018-04-06 00:39, Alexey Ivanov wrote:
> Could you please review the fix for jdk11?
> bug: https://bugs.openjdk.java.net/browse/JDK-8199627
> webrev: http://cr.openjdk.java.net/~aivanov/8199627/webrev.0/
> Windows 10 v1703 provides improved High DPI mode: Per-Monitor v2. 
> Java already supports "Per-Monitor v1" mode. This change extends High
> DPI support in Java: in addition to <dpiAware> element , a new
> <dpiAwareness> element  is added to Java launcher manifest. The
> element <dpiAwareness> is recognized by Windows 10 v1607 and above,
> PerMonitorV2 value is supported by Windows 10 v1703 and above.
> The most notable change for Java applications is that window title bar
> is scaled correctly when application window moves from one monitor to
> another or the scaling changes.
> When building, manifest tool generates warning for unknown
> <dpiAwareness> element in manifest. It is because an older Windows SDK
> is used to build JDK which does not know about an element that was
> added later. The build succeeds despite the warning.
> Thank you in advance.
More information about the awt-dev