You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-dev@xmlgraphics.apache.org by Thierry Kormann <Th...@sophia.inria.fr> on 2000/11/21 16:48:33 UTC
[commit] start error handling on gradients
Some error handling stuffs have been added to gradients.
*** Warning***
The default values of x1, x2, y1, y2 on linearGradient were not conformed to
the current public spec! Who is right??? (current version is conformed to the
spec).
Thierry.
--
Thierry Kormann
email: Thierry.Kormann@sophia.inria.fr http://www.inria.fr/koala/tkormann/
Koala/Dyade/Bull @ INRIA - Sophia Antipolis
Re: [commit] start error handling on gradients
Posted by Vincent Hardy <vi...@eng.sun.com>.
Yup, Christophe is right. I just goofed up when I wrote the bridge.
V.
Christophe Jolif wrote:
>
> Thierry Kormann wrote:
> >
> > Some error handling stuffs have been added to gradients.
> >
> > *** Warning***
> >
> > The default values of x1, x2, y1, y2 on linearGradient were not conformed to
> > the current public spec! Who is right??? (current version is conformed to the
> > spec).
>
> Defaults should be x1=0%, y1=0%, x2=100%, y2=0%. I renember that an
> intermediary draft has a typo in gradient and default was set to 0%, 0%,
> 100%, 100%, this may be the origin of the problem in our code?
>
> --
> Christophe
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: batik-dev-help@xml.apache.org
Re: [commit] start error handling on gradients
Posted by Christophe Jolif <cj...@ilog.fr>.
Thierry Kormann wrote:
>
> Some error handling stuffs have been added to gradients.
>
> *** Warning***
>
> The default values of x1, x2, y1, y2 on linearGradient were not conformed to
> the current public spec! Who is right??? (current version is conformed to the
> spec).
Defaults should be x1=0%, y1=0%, x2=100%, y2=0%. I renember that an
intermediary draft has a typo in gradient and default was set to 0%, 0%,
100%, 100%, this may be the origin of the problem in our code?
--
Christophe