|
![](/i/fill.gif) |
"Thorsten Froehlich" wrote:
> Anyway, it turns out to be more natural to drop the
> initial_clock and final_clock in favor of a start_frame
> and end_frame. This also has the benefit that no hacks
> need to be applied to the core code to get the
> user-specified initial_clock and final_clock.
Um, how then does the user derive the initial_clock and final_clock from the
avaiable clock variables?
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated Feb 16)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Ring: http://webring.povray.co.uk
Post a reply to this message
|
![](/i/fill.gif) |