"Kenneth" <kdw### [at] gmailcom> wrote:

> The main trouble is with the  texture{image_pattern{  syntax.
>
> In its general form for 'masking' use...
>
> texture{
>   image_pattern{
>       png "my_holdout_mask_image_1.png" interpolate 2 // the mask
>       texture_map{TEX_MAP_FOOBAR} // or just texture{...}, the texture to mask
>         }
>        }
[snip]

Sorry, I posted somewhat wrong syntax in that example (the placement of the
curly brackets). I was hastily writing 'on the fly' :-O  It should be:
texture{
  image_pattern{
      png "my_holdout_mask_image_1.png" interpolate 2 // the mask
               }
      texture_map{TEX_MAP_FOOBAR} // or just texture{...}, the texture to mask
       }

.... which makes the following idea partially wrong:

[snip]
> SO, I *could* make 34 complete image_patterns, stick
> them into an array-- which hopefully will accept them and greatly reduce the
> subsequent memory load-- then call *those* in the repeating
> texture{image_pattern{...  later.
>
> [WRONG:] Those 34 image_patterns will necessarily need their '2nd part'
> included as well, the texture to be masked, TEX_MAP_FOOBAR.

Nope, the '2nd part' is not enclosed in the image_pattern{...}.

Well, the whole idea will not work anyway (or *maybe* it would in an array?)--
an image_pattern{...} block cannot be #declared. Same error as before, "not an
RValue." I guess it's the same behavior as trying to #declare a bare
image_map{...}, which likewise doesn't work.

Post a reply to this message