<p dir="ltr">Brecht,</p>
<p dir="ltr">If my thinking is correct, the math is different for subframes before than for subframes after. I may be wrong, though.</p>
<p dir="ltr">Gavin Howard</p>
<div class="gmail_quote">On Jun 28, 2013 7:21 AM, "Brecht Van Lommel" <<a href="mailto:brechtvanlommel@pandora.be">brechtvanlommel@pandora.be</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Gavin,<br>
<br>
On Fri, Jun 28, 2013 at 7:18 AM, Gavin Howard <<a href="mailto:gavin.d.howard@gmail.com">gavin.d.howard@gmail.com</a>> wrote:<br>
> However, I was able to do some thinking about the current state of the<br>
> Attribute class. I know about the AttributeStandard enum and two<br>
> options it has called ATTR_STD_MOTION_PRE and ATTR_STD_MOTION_POST.<br>
> Currently, under those, an Attribute only holds one mesh. Based on<br>
> suggestions by Brecht and Stuart, I was thinking of extending those<br>
> two to handle multiple meshes. The reason I want to keep them is that<br>
> steps before the frame need to be treated differently from steps after<br>
> the frame.<br>
..<br>
> Also, I would like current devs to comment on my thoughts for<br>
> extending ATTR_STD_MOTION_PRE and ATTR_STD_MOTION_POST.<br>
<br>
I'm not sure what you propose to do exactly, but in my previous mail I<br>
explained how you could extend attributes to store data for multiple<br>
frames. Probably if you do that it doesn't make sense anymore to make<br>
a distinction between PRE and POST, and maybe just store it all in a<br>
single ATTR_STD_MOTION attribute that contains frame before and after<br>
the current frame?<br>
<br>
Brecht.<br>
_______________________________________________<br>
Soc-2013-dev mailing list<br>
<a href="mailto:Soc-2013-dev@blender.org">Soc-2013-dev@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/soc-2013-dev" target="_blank">http://lists.blender.org/mailman/listinfo/soc-2013-dev</a><br>
</blockquote></div>