There is an AWT desktop property that will enable JDK6 apps. to determine the
desktop preferred status of anti aliasing on text. Look here:
http://java.sun.com/javase/6/docs/api/java/awt/doc-files/DesktopProperties.html
All the values with LCD in the name are the ones related to sub-pixel
See, the thing is you keep on writing sub-pixel aliasing, but as far as I'm
aware there are two implementations for that: JDK-based and native-based
(ClearType) so it isn't immediately clear to me which one LCD_* refers to.
If you look at the comment section of Chet's blog you will find this:
Sorry, a few small corrections :) I forgot to account for the fact that the
desktop might support ClearType rendering but the user disabled them.
KEY_TEXT_ANTI_ALIASING:
DEFAULT: Anti-aliasing is on for JDK 1.6 if desktop anti-aliasing is enabled,
OFF for JDK 1.5
ON: Anti-aliasing is on, using
[EMAIL PROTECTED] wrote:
Sorry, a few small corrections :) I forgot to account for the fact that the
desktop might support ClearType rendering but the user disabled them.
KEY_TEXT_ANTI_ALIASING:
DEFAULT: Anti-aliasing is on for JDK 1.6 if desktop anti-aliasing is enabled,
OFF for JDK 1.5
[EMAIL PROTECTED] wrote:
DEFAULT: Anti-aliasing is on for JDK 1.6 if desktop
anti-aliasing is enabled, OFF for JDK 1.5
It may not be clear to others - or perhaps you- but
your comments above
refer to *Swing* behaviours. Not 2D.
2D's default on all (Sun) implementations to date is
[EMAIL PROTECTED] wrote:
Why couldn't ON (from Java 1.2) mean grayscale AA up to 1.5 and in 1.6 become
general AA? Isn't that a superset? Could it really break any practical form of
backwards compatibility?
It would be an incompatible change.
And what would 2D pick when you did say ON?
Fair enough, thanks Phil.
Is there a chance of augmenting the documentation with these details? That is,
mention that whether JDK or native font rendering is used is an implementation
detail (that cannot be configured) and that ON means grayscale anti-aliasing. I
don't think the existing
