[
https://issues.apache.org/jira/browse/PIVOT-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel updated PIVOT-393:
-------------------------
Attachment: GrayscaleRadioText.png
I'm on Windows XP, but the same thing can be noticed in the
kitchensink-ubuntu9.zip screenshots, so it's not platform specific. In the
GrayscaleRadioText screenshot (400% zoom) you can see that most of the text
uses LCD AA. You'll see that the LCD AA text is composed of multi-colored
pixels (blue, orange, red, yellow, etc) for black text. Then you'll notice that
the text for radio buttons is composed only of grayscale pixels (black and
shades of gray) which is just the good ol' Grayscale AA. Similarly, checkboxes
also use Grayscale AA. All other components that I checked look good - they use
LCD AA as expected.
> Certain UI components do not properly respect system text anti-aliasing hints
> -----------------------------------------------------------------------------
>
> Key: PIVOT-393
> URL: https://issues.apache.org/jira/browse/PIVOT-393
> Project: Pivot
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Greg Brown
> Assignee: Greg Brown
> Fix For: 1.5
>
> Attachments: GrayscaleRadioText.png, kitchensink-ubuntu9.zip,
> pivot-393.patch, pivot-393_test_winXp.zip,
> pivot_aa-tests_winXP_2010-04-15.zip, pivot_aa_test_windo...@64.zip,
> rhel5-1.6.0_16.png, sink-new.png, sink-old.png,
> text-test-winxp-java1.6.0.16-cleartype.jpg, winxp_cleartype.zip
>
>
> Some components render text using the drawString() method of Graphics2D and
> properly set the text rendering hints using the getTextAntialiasingHint()
> method in the Platform class. However, other components use a glyph vector
> that does not currently respect the text rendering hints. These components
> should be updated to use a FontRenderContext containing the correct text
> rendering hints:
> http://java.sun.com/javase/6/docs/api/java/awt/font/FontRenderContext.html#FontRenderContext(java.awt.geom.AffineTransform,%20java.lang.Object,%20java.lang.Object)
> Also, there is a minor issue with the use of getTextAntialiasingHint(): the
> AWT "awt.font.desktophints" property may contain multiple hints (e.g. on my
> desktop it also defines KEY_TEXT_LCD_CONTRAST) and Pivot is only looking at
> KEY_TEXT_ANTIALIASING. Additional methods should be added to support the
> other values.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
