> [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 > "OFF."
> 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. Right, so 2D is really out of the picture for most of this stuff. We're just discussing AWT and Swing. > Wrong. the rendering hint value "ON" means greyscale > AA. It does not > mean desktop default. 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? > And on windows "ON" is not going to correspond to any > windows desktop > setting. > For windows its either "OFF", "GASP" (== windows > standard), or > "LCD_HRGB"(~=cleartype) Thanks for the mapping. I was wondering about that. In any case, you wrote in another post that whether LCD_HRGB maps to JDK-rendering or ClearType rendering is a non-configurable implementation detail. Fair enough, but then shouldn't ON also map to an abstract concept of "anti-aliasing is on" and let the implementation detail what AA renderer is appropriate? Gili [Message sent by forum member 'cowwoc' (cowwoc)] http://forums.java.net/jive/thread.jspa?messageID=297505 =========================================================================== 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".
