This is probably due to the fact that we use different rendering
pipelines in some cases when the colors are translucent (for example, we
may use X11 requests to render on Linux and Solaris when the colors are
solid, and then we may use "readback, modify pixels, writeback"
mechanisms to deal with translucent requests. Sometimes the exact
pixel-for-pixel rasterization of the two pipelines doesn't match. It is
a bug, but the fix may be hard. If you could submit a bug with a
smaller (standalone) test case then it could be tracked...
...jim
jav...@javadesktop.org wrote:
Hi all,
I have a weird problem which may be a bug, but hopefully has a solution. I am
drawing a histogram whose bins are coloured according to an arbitrary colour
map. This involves drawing a series of filled rectangles whose height is
proportionally to the frequency of the bin, and then drawing an outline across
the tops of these rectangles.
This works fine for colour maps with no transparency; however, when I want to
apply transparency to the rectangles, they render incorrectly, and in a
seemingly unpredictable way (see this image:
http://www.typically.net/FTP/histogram_bug_all.png ).
The exact same code is used to render both instances, which is why I'm thinking
this must be a Java2D bug... The rendering code (where g is the Graphics2D
instance) is:
===========================================================================
To unsubscribe, send email to lists...@java.sun.com and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
lists...@java.sun.com and include in the body of the message "help".
