<div dir="ltr">Hi,<br><br><div class="gmail_quote">On Wed, Oct 1, 2008 at 11:37 PM, lorenzo pierfederici <span dir="ltr"><<a href="mailto:lpierfederici@gmail.com">lpierfederici@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
mmh, maybe a bit off-topic...<br>
<br>
but it would be great if we could have, in this "animation container",<br>
the ability to "animate" a property by connecting it to another<br>
property, so that when the source changes the destination gets<br>
updated.</blockquote><div><br>This is the whole idea behind separating drivers from normal animation data. Thus, drivers become attached to the properties or so, instead of existing in animation containers.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This could have its own node editor view with nodes sockets<br>
auto-generated from properties, where we could manipulate connections<br>
and use operators like offset, clamp, sum, and all the way up to<br>
constraints and custom python expressions.<br>
<br>
I think something like make_connection(), break_connection() could fit<br>
the Data API scope... but I guess it depends on how the animation<br>
system will relate to it.<br>
<font color="#888888"><br>
lorenzo<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<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>
</div></div></blockquote></div><br></div>