[Bf-committers] [Bf-blender-cvs] SVN commit: /data/svn/bf-blender [36047] trunk/blender/source/blender/ python/intern/bpy_rna.c: change to fcurve keyframe coords broke simplify addon since the property

[Joshua Leung]

If you're talking about why the fcurve keyframe coords are wrapped as
PROP_NONE instead of as vectors, the current problem is that wrapping
these that way tags them as being subject to units-system tinkering,
which is in most cases completely and utterly wrong (i.e. time or
rotations in meters/inches?!).

On Fri, Apr 8, 2011 at 1:50 PM, Matt Ebb <matt at mke3.net> wrote:
> On Fri, Apr 8, 2011 at 11:40 AM, Campbell Barton <ideasman42 at gmail.com> wrote:
>> Revision: 36047
>>          http://projects.blender.org/scm/viewvc.php?view=rev&root=bf-blender&revision=36047
>> Author:   campbellbarton
>> Date:     2011-04-08 01:40:54 +0000 (Fri, 08 Apr 2011)
>> Log Message:
>> -----------
>> change to fcurve keyframe coords broke simplify addon since the property
>> was no longer wrapped by python as a vector. now fixed size float arrays
>> with PROP_NONE subtype are wrapped as vectors since its convenient to
>> have x/y access.
>
> Is that all fixed size float arrays of rna size 3? or all float arrays
> in general? Sounds like if it is meant to be an array of single floats
> (for example) it wouldn't be right to wrap as a python vector type?
>
> cheers
>
> Matt
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>