Hi,<br><br>These are two different concepts. Sure, they share similarities (i.e. stack based operations), and indeed I've based much of the F-Curve Modifier code on the constraint code. However, whereas Constraints are limited to matrix-based operations INVOLVING DEPENDENCIES at the end of the evaluation flow, F-Curve Modifiers can operate on ANY property (be it transforms, material or lighting properties) but MUST NOT INVOLVE DEPENDENCIES as they're evaluated at the start of the evaluation process when absolutely no dependencies can be taken into account. For that kind of low-level dependencies, you'd want to use Drivers not F-Curve Modifiers.<br>
<br>Hopefully that clarifies your question :)<br>Aligorith<br><br><div class="gmail_quote">2009/3/20 Wahooney <span dir="ltr"><<a href="mailto:wahooney@wahooney.net">wahooney@wahooney.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#3333ff">
<font size="-1"><font face="Tahoma">I was looking at the f-curve
modifier stuff and I was wondering if it wouldn't be best to merge
constraints and modifiers together, either as just constraints or just
modifiers. This would give a unified manner of affecting f-curves
rather than two.<br>
<br>
If this is already the case just ignore me :)<br>
<br>
Keith Boshoff<br>
</font></font>
</div>
<br>_______________________________________________<br>
Bf-taskforce25 mailing list<br>
<a href="mailto:Bf-taskforce25@blender.org">Bf-taskforce25@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-taskforce25" target="_blank">http://lists.blender.org/mailman/listinfo/bf-taskforce25</a><br>
<br></blockquote></div><br>