POV-Ray : Newsgroups : povray.beta-test : Small change in trace() doc (6.1.4.6) Server Time
5 Nov 2024 05:24:53 EST (-0500)
  Small change in trace() doc (6.1.4.6) (Message 1 to 3 of 3)  
From: Gilles Tran
Subject: Small change in trace() doc (6.1.4.6)
Date: 8 Sep 2001 16:34:21
Message: <3B9A8158.5BC3035F@inapg.inra.fr>
I guess that
  #if (Norm.x != 0 | Norm.y != 0 | Norm.z != 0)
 could now be replaced by
    #if (vlength(Norm)!=0)

G.
--

**********************
http://www.oyonale.com
**********************
Graphic experiments
Pov-ray gallery


Post a reply to this message

From: ingo
Subject: Re: Small change in trace() doc (6.1.4.6)
Date: 8 Sep 2001 17:52:03
Message: <Xns9116F2CB0C3A2seed7@povray.org>
in news:3B9A8158.5BC3035F@inapg.inra.fr Gilles Tran wrote:

>     #if (vlength(Norm)!=0)
> 

Yes, done


Ingo

-- 
Photography: http://members.home.nl/ingoogni/
Pov-Ray    : http://members.home.nl/seed7/


Post a reply to this message

From: Anders K 
Subject: Re: Small change in trace() doc (6.1.4.6)
Date: 15 Sep 2001 17:41:49
Message: <3ba3cb1d$1@news.povray.org>
> I guess that
>   #if (Norm.x != 0 | Norm.y != 0 | Norm.z != 0)
>  could now be replaced by
>     #if (vlength(Norm)!=0)

What's wrong with #if (Norm != <0, 0, 0>)? (Tries it...) Oh, now I see.
"Parse Error: Float expected but vector or color expression found". I see
from the docs that (Norm != <0, 0, 0>) evaluates to a vector. This could
confuse a lot of users. The docs' explaination is, "admittedly this isn't
very useful but it's consistent with other vector operations". Why?

I'm sorry if this has been said before, but it seems annoying to have to
write #if (v1.x = v2.x & v1.y = v2.y & v1.z = v2.z) instead of #if (v1 = v2)
to test whether two vectors are equal. If I really wanted to know seperately
whether two vectors' x, y, and z coordinates are equal, I could write <v1.x
= v2.x, v1.y = v2.y, v1.z = v2.z>. Oh well, I guess it's too late now.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.