A good example would be a flashing light.

--
Mike

wk: mik### [at] pyxiscom  www.pyxis.com
hm: mwe### [at] sciticom  www.geocities.com/mikepweber


"Rick Adams" <ben### [at] xprtnet> wrote in message
news:benboomREMOVE_THIS_PART-1A7DD9.07502819042000@news.povray.org...
> In article <38fd313b@news.povray.org>, "Bob Hughes"
> <per### [at] aolcom?subject=PoV-News:> wrote:
>
>
> > | I don't do much animation work but I believe the difference is that
the
> > | first example will cause the death ray to appear at clock cycle 0.5
and
> > | persist until it reaches a value of one - until the last frame of the
> > | animation. With the second example you can have the death ray appear
at
> > | a clock value of 0.3 and then dissapear at the clock value of 0.5. The
> > | second method offers a little more flexibility than does the first.
> >
> > That's pretty much it, and for simplicity really.  You have to start
> > nesting those "#if" directives to get the same
> > result.  Can get difficult to follow.
>
> Okay, I understand. It wasn't an issue in the animation I'm doing now
> since I send the death ray off out of the picture, never to be seen
> again (it's more like the rays they used in Forbidden Planet, it you
> remember that one), but your way makes them able to disappear on cue,
> too. That's probably lots more useful for most apllications.
>
> Thanks, everybody.

Post a reply to this message