Thanks Campbell! :-D --Nathan
On Sun, Oct 10, 2010 at 9:53 PM, Campbell Barton <[email protected]> wrote: > On Mon, Oct 11, 2010 at 1:13 AM, Nathan Vegdahl <[email protected]> wrote: >> I'm unsure if this is a bug, so I'll hold off filing a bug report. >> It seems that it's not possible to create custom properties on bones >> or pose bones. >> >> This works: >> bpy.types.Object.new_prop = bpy.props.FloatProperty() >> But these don't: >> bpy.types.Bone.new_prop = bpy.props.FloatProperty() >> bpy.types.PoseBone.new_prop = bpy.props.FloatProperty() >> >> Trying to access the new custom properties results in this for objects: >> 0.0 >> And this for the other two: >> (<built-in function FloatProperty>, {}) >> >> Is this by design? And if so, can it be changed? I could really use >> custom bone properties for the work I'm doing on the auto-rigging >> system, as I would like to create an enum property on pose bones (or >> bones, either way). >> >> --Nathan Vegdahl > > good find, fixed r32407. > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
