-
Bug
-
Resolution: Fixed
-
P4
-
1.2.1, 6
-
b73
-
generic, x86
-
windows_xp
On Windows, GraphicsConfiguration.getNormalizingTransform() will always return
the identity transform for screen devices, i.e. 72 dpi, since getXResolution() and
getYResolution() both return hardcoded values of 72. Windows typically returns
a screen resolution of 96 dpi, and in fact, Toolkit.getScreenResolution() will
query the native system and return a value of 96 dpi by default on Windows. We
should update Win32GraphicsConfig so that it fetches the appropriate value from
native code as we do in WToolkit and in X11GraphicsConfig. This will be important
going forward for resolution independent GUIs in Swing.
the identity transform for screen devices, i.e. 72 dpi, since getXResolution() and
getYResolution() both return hardcoded values of 72. Windows typically returns
a screen resolution of 96 dpi, and in fact, Toolkit.getScreenResolution() will
query the native system and return a value of 96 dpi by default on Windows. We
should update Win32GraphicsConfig so that it fetches the appropriate value from
native code as we do in WToolkit and in X11GraphicsConfig. This will be important
going forward for resolution independent GUIs in Swing.
- duplicates
-
JDK-6522214 java.awt.DisplayMode should support getDpi()
-
- Closed
-