harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Okomin" <ilya.oko...@gmail.com>
Subject Re: [classlib] HARMONY-2055 - non bug difference.
Date Wed, 06 Dec 2006 11:00:40 GMT
On 12/6/06, Alexey Petrenko <alexey.a.petrenko@gmail.com> 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

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message