<AWT Dev> [11] JDK-8196006: java/awt/Frame/SetMaximizedBounds/SetMaximizedBounds.java fails
Sergey Bylokhov
Sergey.Bylokhov at oracle.com
Sat Feb 3 06:49:33 UTC 2018
Hi, Shashi.
Before this fix this test was executed on all screens on the system.
Why have you changed it to test only main screen?
If I understand the code correctly the test checks the size which is
passed to frame.setMaximizedBounds() and the size which is returned by
frame.getBounds(). In both cases the size should be in the users
space(not in pixels). Why additional transform(added in the fix) is
necessary?
On 01/02/2018 20:39, Shashidhara Veerabhadraiah wrote:
> Hi All, Please review a fix for the test bug.
>
> Bug: https://bugs.openjdk.java.net/browse/JDK-8196006
>
> Webrev: http://cr.openjdk.java.net/~sveerabhadra/8196006/webrev.00/
>
> Summary: This test fails on a hidpi monitor whereas passes on a normal
> monitor. Now the calculations are altered to take care of the scaling
> factor of the primary display unit. Now this test passes on both normal
> and hidpi monitors.
>
> Thanks and regards,
>
> Shashi
>
--
Best regards, Sergey.
More information about the awt-dev
mailing list