[Bf-committers] Re: [Bf-blender-cvs] CVS commit: blender/source/blender/python BPY_interface.c blender/source/blender/python/api2_2xBone.c

[Willian Padovani Germano]

----- Original Message -----
From: "Joseph Gilbert" <models@paposo.com>
To: <bf-committers@blender.org>
Sent: Wednesday, May 05, 2004 8:41 AM
Subject: RE: [Bf-committers] Re: [Bf-blender-cvs] CVS commit:
blender/source/blender/python BPY_interface.c
blender/source/blender/python/api2_2xBone.c


> Willian solved this problem by making the verts and faces in
> an NMesh PyObject's and then have the user call NMesh.update() to update the
> underlying C data.

Oops, that was already done in the original 2.25 API, the credit is not mine.
We've learned a lot from the old implementations, good things there.  Not my
time but from comments in the code -- from what I remember, Strubi wrote those
parts, right oldtimers?

> What I'm playing with is an 'internal' Armature.update()
> that will update the Bone C struct data upon adding the bone to the
> arnature.

An update function may be the way, yes.  We all agree that deallocating blender
objects inside python ones should be avoided.  Even an error msg is better, tell
the script writer that the script must behave nicely (they shouldn't create
pybones and leave them unused / unlinked), they are also programmers : ).

--
Willian, wgermano@ig.com.br