[Bf-taskforce25] Constraints and F-Curve Modifiers

[Joshua Leung]

Hi,

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.

Hopefully that clarifies your question :)
Aligorith

2009/3/20 Wahooney <wahooney at wahooney.net>

>  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.
>
> If this is already the case just ignore me :)
>
> Keith Boshoff
>
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-taskforce25/attachments/20090320/bb7a561e/attachment.htm