<AWT Dev>  RFR for JDK-8199627: Use "Per-Monitor V2" High DPI awareness for Windows 10 v1703
alexey.ivanov at oracle.com
Mon Apr 16 12:49:19 UTC 2018
I haven't found a way to suppress this warning. I tried. There's no way
to suppress warnings from mt.exe  unfortunately.
We're using Visual Studio 2013 to build JDK, the element was added in
2016. Newer versions of Windows SDK should recognise the element.
Yes, it works as intended. It's recognised by Windows 10 v1703 and later
and changes High DPI mode. Other versions of Windows are not affected.
I should've included build-dev into the review process as it affects
Can the output of mt.exe be redirected? If it's successful, then its
output gets ignored.
On 16/04/2018 13:26, Magnus Ihse Bursie wrote:
> Hi Alexey,
> 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. 
>> 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