> Maybe this would be clearer if the keyword wouldn't be hollow but
> something else. 'Hollow' does have a meaning which simply doesn't fit
> its purpose.

The thing that bugs me about "hollow," besides its ambiguity, is that I
almost always want it. My only experience with hollow is this: I make a
media filled object and render it, and there's no media. "Oops, I forgot to
say 'hollow'." I add the keyword and the image renders the way I intended.
It seems to be much more frequent that you want an object to be hollow than
that you don't.

So, I'd suggest removing it and adding a "no_media" keyword that specifies
when an object *shouldn't* allow media inside it. Even better:
"no_external_media" so that you can disallow external media while still
having internal media that is different. (For instance, a ball of red glass
in a room that has blue fog.)

 - Slime
 [ http://www.slimeland.com/ ]

Post a reply to this message

Slime wrote:
> So, I'd suggest removing it and adding a "no_media" keyword that specifies
> when an object *shouldn't* allow media inside it.

Indeed.

What was the original purpose of the keyword, anyway? I would guess that 
Povray performs some speed optimization that is not possible once the 
keyword is added, but if so I can't see the result in my render times.

Otherwise, it would seem obvious to me that adding interior { media { 
... } } means that you want media, regardless of what other keywords are 
or aren't present. :-)

-- 
William Tracy
afi### [at] gmailcom -- wtr### [at] calpolyedu

One major known problem with supporting V-class is the complexity of its 
PCI bus adapter (EPIC and SAGA). Support for the V-class isn't going to 
happen until some really masochistic person who has access to a V-class 
is, uh, challenged by this.
     -- from the Linux-on-HPPA FAQ

Post a reply to this message