> [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.
ON says "Text antialiasing hint value -- text rendering is done with some form of antialiasing." Read "some form" repeatedly until you realize that it isn't obvious that this hint refers to "greyscale AA" exclusively. > 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. So, why not LCD_VRGB? or HBGR? This is one of the super-absurd logics of Java - how the heck is I supposed to know which type of display the user has, and in what direction that display is orientated? What about a "PRETTIEST" hint? [Message sent by forum member 'stolsvik' (stolsvik)] http://forums.java.net/jive/thread.jspa?messageID=298124 =========================================================================== 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".
