JDK-6274842 : RFE: Provide a means for a custom look and feel to use desktop font antialiasing settings.
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2005-05-23
  • Updated: 2018-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Related Reports
Duplicate :  
Relates :  
Relates :  
Relates :  
Several Swing provided look and feel implementations (Metal, GTK, Windows) have
been augmented in JDK 6 (mustang) to automatically detect and use the desktop
text antialiaing settings (eg windows standard font smoothing or LCD text)
However the desktop settings are provided via internal JDK means which
aren't exposed to developers.

This means that a custom look and feel, or even a single custom component,
can't obtain the same information.

For example if a custom component were to be used in the windows look and
feel, whilst it can pick up the desktop fonts from UIDefaults, and even
changes in these fonts, it cannot use or be notified of the desktop.

It would be useful to expose this information in a directly useful way
for a custom look and feel, or perhaps for a custom component to be
be able tap into the same mechanisms as used by Swing.

###@###.### 2005-05-23 22:05:21 GMT

I guess that the fix for 6288260 is another issue. Fow a few reasons. For axample our shared code does not use this property directly, it uses some internal intermediate classes and client properties: - SwingUtilities2.AA_TEXT_PROPERTY_KEY. Note that this propertie is used by JComponent.getClientProperty - SwingUtilities2.AATextInfo - SwingUtilities2.drawString etc Also it is unclear how desktop properties are related to "awt.useSystemAAFontSettings" option.

JDK-6288260 was filed shortly after this bug and resolved by adding desktop property support. See https://docs.oracle.com/javase/8/docs/api/java/awt/doc-files/DesktopProperties.html This resolves the case for custom components L&Fs.