x, y and z are just *shortcuts* for <1,0,0> <0,1,0> and <0,0,1>
respectively. As you know vectors aren't used exclusively for
transformations (i.e. rotations, translations and scale), so they must work
the same way in any circumstance. I mean, if I write y, I mean <0,1,0> (what
otherwise?). So, since rotate, translate and scale need a vector, and since
x, y and z are those vectors I mentioned above and HAVE to work the same way
everywhere, if you write scale 2*x the parser HAS to read <2,0,0>. I
personally never used to scale individual axes, but think that those
warnings are just enough.

--
Jonathan.

"Dave Dunn" <poi### [at] aolcom> ha scritto nel messaggio
news:3C07F02B.A1CD5A65@aol.com...
>
>
> Warp wrote:
>
> >   What should be done is that the warning is replaced with an error.
>
> That's a bit extreme, isn't it? It is obviously easier, from a user's
> standpoint, to type scale y*.1 than scale <1,.1,1>, and most of us do it
> anyway, ignoring the warning. The fact that POV is internally groaning
because
> we tried to divide by zero should be immaterial to the user, who assumes
by
> scaling only one axis that the other ones will not be scaled by anything.
>
>

Post a reply to this message