You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Alexey Petrenko <al...@gmail.com> on 2006/12/06 10:23:15 UTC
[classlib] HARMONY-2055 - non bug difference.
Guys,
I would say that HARMONY-2055[1] is a non bug difference from RI.
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)
Re: [classlib] HARMONY-2055 - non bug difference.
Posted by Alexey Petrenko <al...@gmail.com>.
Since nobody objects I'll close this issue.
SY, Alexey
2006/12/7, Tony Wu <wu...@gmail.com>:
> Ok, I see. The difference comes from different design. Thank you for
> explanation.
>
> +1 to file as a non-bug difference.
>
> On 12/7/06, Alexey Petrenko <al...@gmail.com> wrote:
> > 2006/12/6, Tony Wu <wu...@gmail.com>:
> > > 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?
> > It looks like RI has to transforms in their Graphics2D implementation:
> > from 0,0 to client area and user transform. User can not override
> > first transfrom in this case.
> > Our implementation has just one transform. This makes implementation
> > more clean and easy and let to avoid unnecessary transform
> > composition.
> >
> > SY, Alexey
> >
> > > On 12/6/06, Ilya Okomin <il...@gmail.com> wrote:
> > > > On 12/6/06, Alexey Petrenko <al...@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
> > > >
> > > >
> > >
> > >
> > > --
> > > Tony Wu
> > > China Software Development Lab, IBM
> > >
> >
>
>
> --
> Tony Wu
> China Software Development Lab, IBM
>
Re: [classlib] HARMONY-2055 - non bug difference.
Posted by Tony Wu <wu...@gmail.com>.
Ok, I see. The difference comes from different design. Thank you for
explanation.
+1 to file as a non-bug difference.
On 12/7/06, Alexey Petrenko <al...@gmail.com> wrote:
> 2006/12/6, Tony Wu <wu...@gmail.com>:
> > 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?
> It looks like RI has to transforms in their Graphics2D implementation:
> from 0,0 to client area and user transform. User can not override
> first transfrom in this case.
> Our implementation has just one transform. This makes implementation
> more clean and easy and let to avoid unnecessary transform
> composition.
>
> SY, Alexey
>
> > On 12/6/06, Ilya Okomin <il...@gmail.com> wrote:
> > > On 12/6/06, Alexey Petrenko <al...@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
> > >
> > >
> >
> >
> > --
> > Tony Wu
> > China Software Development Lab, IBM
> >
>
--
Tony Wu
China Software Development Lab, IBM
Re: [classlib] HARMONY-2055 - non bug difference.
Posted by Alexey Petrenko <al...@gmail.com>.
2006/12/6, Tony Wu <wu...@gmail.com>:
> 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?
It looks like RI has to transforms in their Graphics2D implementation:
from 0,0 to client area and user transform. User can not override
first transfrom in this case.
Our implementation has just one transform. This makes implementation
more clean and easy and let to avoid unnecessary transform
composition.
SY, Alexey
> On 12/6/06, Ilya Okomin <il...@gmail.com> wrote:
> > On 12/6/06, Alexey Petrenko <al...@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
> >
> >
>
>
> --
> Tony Wu
> China Software Development Lab, IBM
>
Re: [classlib] HARMONY-2055 - non bug difference.
Posted by Tony Wu <wu...@gmail.com>.
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 <il...@gmail.com> wrote:
> On 12/6/06, Alexey Petrenko <al...@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
>
>
--
Tony Wu
China Software Development Lab, IBM
Re: [classlib] HARMONY-2055 - non bug difference.
Posted by Ilya Okomin <il...@gmail.com>.
On 12/6/06, Alexey Petrenko <al...@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