[EMAIL PROTECTED] wrote:
Fred,
One thing I don't understand is why changing KEY_TEXT_ANTIALIASING from its
original value to VALUE_TEXT_ANTIALIAS_ON would break anything. Shouldn't
VALUE_TEXT_ANTIALIAS_ON look up the desktop preferred anti-aliasing and use
that instead?
Wrong. If you read the JDK docs "ON" has been there since JDK 1.2 in
1998 and has always meant
do greyscale AA.
Java 2D does not pick up the desktop setting. AWT desktop properties is
what does that and
Swing uses that to tell 2D what to use.
One thing I still don't understand is: what value (or values) are associated
with:
- The JDK sub-pixel rendering
- Native sub-pixel rendering
There is no distinction. Its the same LCD_HRGB hint. What happens under
the covers
is an implementation issue.
-phil.
the VALUE_TEXT_ANTIALIAS_* values don't make this distinction obvious at all :(
[Message sent by forum member 'cowwoc' (cowwoc)]
http://forums.java.net/jive/thread.jspa?messageID=297246
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
