[Bf-committers] FCurve Python update patch

Dan Eicher dan at eu.phorio.us
Thu Jul 18 17:54:50 CEST 2013


Hi,

I did a quick check and it does indeed look like a simple matter of missing
update calls.

It's an easy fix but it's too close to release to be messing around with
something like this so...

Dan


On Wed, Jul 17, 2013 at 10:57 AM, Tom Edwards <contact at steamreview.org>wrote:

> Here's a script:
>
> import bpy
>
> o = bpy.context.active_object
> if not o.animation_data: o.animation_data_create()
>
> a = o.animation_data.action = bpy.data.actions.new("Test Action")
>
> c = a.fcurves.new(data_path="location",index=2)
>
> c.keyframe_points.add(3)
> c.keyframe_points[0].co = [0, 0]
> c.keyframe_points[1].co = [4, 1.5]
> c.keyframe_points[2].co = [8, 0]
>
> This is what I see (note the orange handle line):
> http://img46.imageshack.us/img46/8609/aath.png
>
> Editing the curve or even starting an edit then cancelling it causes the
> handles to pop into the correct position.
>
> On 17/07/2013 5:46, Dan Eicher wrote:
> > HI,
> >
> > Do you have some code that shows how this fails because it really should
> > happen automagically, probably just a missing update event somewhere.
> >
> > Dan
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>


More information about the Bf-committers mailing list