Phil,
Can you answer just one question? Has the Java2D team talked to the Swing
team about this problem?
It's amazing that as long as Swing and Java2D have been out (even in beta)
that no one has attempted to address this problem. I've seen Swing code
that checks whether it is running a 1.2.x VM so I know they can program for
Java2 differences. I'll bet they are not even aware of what should be
changed. Or they may feel it is a Java2D problem instead since
Windows-based anti-aliased text looks fine with Swing. Maybe it's Java2D's
AA algorithm that erroneously extends the length of text. I would expect an
AA text string to be the same length as a non-AA string, but just more
readable. This is how I see other AA rendering on my Windows NT and
Macintosh machines!
-Ron
> Its not quite that simple, since getStringBounds() needs to know the G2D
> It is believed that Swing's metrics calculations are structured
> in a way that
> assumes the metrics are not affected by anything. This would probably
> require significant changes in Swing, possibly with some
> performance impact.
> The Swing team will look into how they should handle this, but its not
> going to make a release this year, so the recommendation is not
> to use A-A text.
>
> -Phil.
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 2D Home Page: http://java.sun.com/products/java-media/2D/
