POV-Ray : Newsgroups : povray.unofficial.patches : UVPOV 5.2a parser bug : Re: UVPOV 5.2a parser bug Server Time
2 Nov 2024 15:25:53 EDT (-0400)
  Re: UVPOV 5.2a parser bug  
From: Ken
Date: 16 Jun 1999 10:42:17
Message: <3767B4E3.56E63F34@pacbell.net>
Thorsten Froehlich wrote:
> 
> In article <3766F4D6.DFC19439@Kopp.com> , Nathan Kopp <Nat### [at] Koppcom>
> wrote:
> 
> > That's how you do layered textures.  And this parser keeps looking harder
> > and harder to fix.  :-(  ...and it looked so easy at first.
> 
> Yes, layered textures _inside_ object declarations, but if I read this right
> 
> #declare T_Wood34 =
> texture { T_Wood32 }
> texture  { ... }
> 
> should (or will) only declare
> 
> #declare T_Wood34 =
> texture { T_Wood32 }
> 
> and I suppose that the parser complains about the second texture { ... } if
> the #if .. #end isn't there.  I would suggest to declare each of the
> textures and then use each of them in the object which still gives a layered
> texture.
> 
>     Thorsten
> 
> ____________________________________________________
> Thorsten Froehlich, Duisburg, Germany
> e-mail: Tho### [at] csicom
> 
> Visit POV-Ray on the web: http://mac.povray.org


  Dating back at least as far as Pov v2.2 it has been valid to declare
textures as previously illustrated i.e.

#declare T1 = 
texture { ... }
texture { ... }

object { thing texture { T1 }}

  I have designed and used so many layered textures this way I can verify it's
legitimacy.

-- 
Ken Tyler

mailto://tylereng@pacbell.net


Post a reply to this message

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