Re: Frame System

--===============1711262410==
Content-Type: multipart/alternative; 
	boundary="----=_Part_83961_20846269.1159858236702"

------=_Part_83961_20846269.1159858236702
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Ammm what you didn't understood, is that i didn't declare by myself each one
i  declared some control points, and with my parser calculate the tween
between them.
(each frame) so you would have all the positions, may be i didn't express
myself correctly.
----
IMO these defines should never make it into the povray code
-----

Why? I've used them, and they worked.
(watch the video i sent you, there is a render (animated) example of it)

The defines generates automaticaly, when a change would be made within a
tween
such like Macromedia Flash works.

----
All animated
object/properties should be calculated for a single frame, exported to
povray and rendered.
----
This would be a very bad idea when writing big files.
If i make a povray file of lets say  10 MB, in the case you mention i would
need to write a 10 MB file and render (read) a 10 megabytes for each frame ,
instead of writing  a 10.1 MB file once.

Also stating that the defines i mentioned are POVRay code.
The advantage of that peace of code that it contains the history of the
animation.
To post it this way

------
Objects could be visible only in
some frames. That all would be incredible difficult with the povray defines.
-----
I'll be more explicity this time, maybe i am not expressing the things
properly.

#if (clock > 0 )     // This is povray code and it should be generated
(ONCE) by
                          the control points and the process of the kpov
file format. where
                         it would be added the animations control points and
the tween basis
                         then it generates the "code" for povray to render
(the every calculated     frame)
 gf1 = 0.000000 ;
  gf2 = 0.350000 ;
 gf3 = -0.980922 ;
  rf2 = 0.000000 ;
#end
 #if (clock > 1 )
 gf1 = 0.000000 ;
  gf2 = 0.350000 ;
 gf3 = -0.962587 ;
  rf2 = 0.049835 ;
#end

------=_Part_83961_20846269.1159858236702
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Ammm what you didn't understood, is that i didn't declare by myself each one<br>i&nbsp; declared some control points, and with my parser calculate the tween between them.<br>(each frame) so you would have all the positions, may be i didn't express myself correctly.
<br>----<br>IMO these defines should never make it into the povray code<br>-----<br><br>Why? I've used them, and they worked.<br>(watch the video i sent you, there is a render (animated) example of it)<br><br>The defines generates automaticaly, when a change would be made within a tween
<br>such like Macromedia Flash works.<br><br>----<br>All animated<br>object/properties should be calculated for a single frame, exported to<br>povray and rendered.<br>----<br>This would be a very bad idea when writing big files.
<br>If i make a povray file of lets say&nbsp; 10 MB, in the case you mention i would need to write a 10 MB file and render (read) a 10 megabytes for each frame , instead of writing&nbsp; a 10.1 MB file once.<br><br>Also stating that the defines i mentioned are POVRay code.
<br>The advantage of that peace of code that it contains the history of the animation.<br>To post it this way<br><br>------<br> Objects could be visible only in<br>some frames. That all would be incredible difficult with the povray defines.
<br>-----<br>I'll be more explicity this time, maybe i am not expressing the things properly.<br><br>#if (clock &gt; 0 )&nbsp;&nbsp;&nbsp;&nbsp; // This is povray code and it should be generated (ONCE) by <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the control points and the process of the kpov file format. where
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it would be added the animations control points and the tween basis<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; then it generates the &quot;code&quot; for povray to render (the every calculated&nbsp;&nbsp;&nbsp;&nbsp; frame)<br>
&nbsp;gf1 = 0.000000 ;<br>&nbsp; gf2 = 0.350000 ;<br>&nbsp;gf3 = -0.980922 ;<br>&nbsp; rf2 = 0.000000 ;<br>#end <br>&nbsp;#if (clock &gt; 1 )<br>&nbsp;gf1 = 0.000000 ;<br>&nbsp; gf2 = 0.350000 ;<br>&nbsp;gf3 = -0.962587 ;
<br>&nbsp; rf2 = 0.049835 ;<br>#end <br><br>

------=_Part_83961_20846269.1159858236702--

--===============1711262410==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


List archive and information: https://mail.kde.org/mailman/listinfo/kpovmodeler-devel
--===============1711262410==--