+1
Thanks,
Alexander.
On 09/03/2017 13:48, Sergey Bylokhov wrote:
Looks fine.
Hello,
Could you review the updated fix:
http://cr.openjdk.java.net/~alexsch/8175301/webrev.01
There are two places where D3DSurfaceData.swapBuffers() is called
D3DScreenUpdateManager.run() and
Looks fine.
>
> Hello,
>
> Could you review the updated fix:
> http://cr.openjdk.java.net/~alexsch/8175301/webrev.01
>
> There are two places where D3DSurfaceData.swapBuffers() is called
> D3DScreenUpdateManager.run() and D3DGraphicsConfig.flip(...).
> D3DScreenUpdateManager.run() uses the
Hello,
Could you review the updated fix:
http://cr.openjdk.java.net/~alexsch/8175301/webrev.01
There are two places where D3DSurfaceData.swapBuffers() is called
D3DScreenUpdateManager.run() and D3DGraphicsConfig.flip(...).
D3DScreenUpdateManager.run() uses the surface bounds which are
Hello,
Could you review the fix:
bug: https://bugs.openjdk.java.net/browse/JDK-8175301
webrev: http://cr.openjdk.java.net/~alexsch/8175301/webrev.00
D3DSurfaceData.swapBuffers() is updated to scale passed bounds on
HiDPI display.
Thanks,
Alexandr.