yes, It is an incorrect usage of setTransform. But I 'm a little curious about the cause of this difference. I'm not very familiar with AWT, but in common sence, if you set same transformer then the result will be the same, is it? Or the transformer has not been really set yet?
On 12/6/06, Ilya Okomin <[EMAIL PROTECTED]> wrote:
On 12/6/06, Alexey Petrenko <[EMAIL PROTECTED]> wrote: > > Guys, > > I would say that HARMONY-2055[1] is a non bug difference from RI. +1 I've also checked this test case with using transform() call instead of setTransform() that is recommended to change transform in Graphics. In this case Harmony and RI have the same behavior. Regards, Ilya. Described problem happens because of incorrect usage of > Graphics2D.setTransform method. > Corresponding spec [2] says the following: > === cut === > WARNING: This method should never be used to apply a new coordinate > transform on top of an existing transform because the Graphics2D might > already have a transform that is needed for other purposes, such as > rendering Swing components or applying a scaling transformation to > adjust for the resolution of a printer. > === cut === > > So if nobody object I will close this issue as non-bug-difference. > > SY, Alexey > > [1] http://issues.apache.org/jira/browse/HARMONY-2055 > [2] > http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Graphics2D.html#setTransform(java.awt.geom.AffineTransform) > -- -- Ilya Okomin Intel Enterprise Solutions Software Division
-- Tony Wu China Software Development Lab, IBM
