|
|
"Nicolas Calimet" wrote:
> For B) I suppose you suggest something like:
>
> #declare t1=texture{... transform ...}
> #declare t2=texture{... transform ...}
> ...
> mesh{
> triangle{ ... texture{t1} } // or smooth triangle
> triangle{ ... texture{t2} }
> ...
> }
Yes basically, although I'd use an array.
> which of course requires a lot of memory to declare both
> texture variables and textures in the mesh.
Well, not texture variables, just the textures.
> But what about the following syntax ?
>
> mesh{
> #declare t=texture{ ... transform ...} // #local is more elegant ?
> triangle{ ... texture{t} }
> #declare t=texture{ ... transform ...}
> triangle{ ... texture{t} }
> ...
> }
>
> which might be only a little longer to parse... maybe not.
Interesting. I wonder if it changes anything. I'll try it out. Thanks!
Rune
--
\ Include files, tutorials, 3D images, raytracing jokes,
/ The POV Desktop Theme, and The POV-Ray Logo Contest can
\ all be found at http://rsj.mobilixnet.dk (updated January 6)
/ Also visit http://www.povrayusers.org
Post a reply to this message
|
|