Ha! I looked at the macro and found what I expected:
File I/O.

I was thinking about doing just that, but wasn't sure if there
was some POV-internal (and thus faster, almost everything
hardcoded is faster) way.

So, I'll write my own macro for that, as I always do...

But thanks for the suggestion!

Leroy Whetstone wrote:

> If I understand what you want then using POV3.5 try .
>
> #macro Birth-Field (String)
>  Parse_String(String)
> #end
>
> The String could be  a material{...}, a pigment{} or texture{} or any thing you
> want.
>
> Tim Nikias wrote:
>
> > I need a way to visualize the Birth-Field of my
> > Particle-System. What I came up with, is a macro,
> > which you call like this:
> >
> > Birth_Field(texture{})
> >
> > It would then create and place an object in scene
> > according to the birth-field of the most recent
> > system.
> >
> > Question is: Is there a way can avoid the texture{}?
> > I would like to make it very easy to use, like a
> > POV-Primitive. Thus, I'd like to have the macro
> > handle a material{...}, a pigment{} or texture{}.
> >
> > So, the essential question is:
> > Is it possible for POV to just take the given input
> > and place it in an object, regardless of how it looks
> > like (as long as its in correct POV-SDL, something
> > like
> > Birth_Field( do something )
> > shouldn't work of course...
> >
> > --
> > Tim Nikias
> > Homepage: http://www.digitaltwilight.de/no_lights/index.html
> > Email: Tim### [at] gmxde
>
> --
> Have Fun!

--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmxde

Post a reply to this message