I suspected this already, but I have definite proof that mac and PC do not render simple graphics the same,
for example “fillPoly” hits a different set of pixels on mac and pc, and also drawing partially transparent images
over existing graphics draws slightly different densities. I don’t expect any magic solution, but it sucks if you
care about every pixel.
Well the covered pixels are not specified in the “Java Standard” - each implementation is allowed to render the primitives how it thinks its the best.
However, Apple’s java implementations shares a lot of code with SUN’s - try to paint to a BufferedImage which maybe could give you identical behaviour.
Furthermore, starting with Leopard, Apple uses Sun’s Software renderer instead of their own Quarz based one.
lg Clemens
does anyone have an idea why the JAI and JIIO natives don’t work on XP ? As for example, when enabling natives (there are 6 .dll) under XP, the writing operations don’t work at all. This the option com.sun.media.imageio.disableCodecLib I’m talking about.
Are you sure about that?
Graphics2D requires that the legacy Graphics methods (fillPolygon(…) for example) behave identically to the newer fill(new Polygon(…)) methods.
In turn the Polygon class implements the Shape interface and explicitly states that it conforms to the contract of the Shape interface.
As the Shape interface clearly defines ‘insideness’ of points in relation to any Shape, I think there is certainly an implied contract placed upon the pixels touched by the legacy Graphics methods. (and any other primitive rendering for that matter!)
From what I understand, Apple switched to the Sun Java2D renderer in the latest versions of their implementation of Java 1.5, but the older version used Quartz. Or something like that.
Which version are you running? The official version on Tiger, Leopard, or the DP release for Tiger?