[Bf-committers] EditMesh funcs must no longer be static

Ton Roosendaal ton at blender.org
Fri Oct 8 11:58:50 CEST 2004


I have severe troubles with exposing editmesh to python. This code was  
not meant (at all) to be a stable and accessible API, and it is due to  
change dynamically as well. The last cleanup round wasn't even half  

The editmesh is highly critical code that needs to be fully reliable &  
stable, bothering about what's exported to third parties is not a  
requirement I like to see happening now.

So what's the focus of our Python API? It can't be replacing C  
coding... for that Blender wasn't designed at all.


On 8 Oct 2004, at 08:02, joeedh wrote:

> Tom Musgrove wrote:
>> Hi Joe,
>> as part of a script I'm working on, I've needed a way to get screen  
>> coordinates of a meshes vertice.  So Michael Schardt has written some  
>> code exposing the needed functionality.  I think he plans to make the  
>> patch public shortly.
>> I now have a mesh tool that displaces mesh according to an alphamask  
>> and the cursor location.  (Ie you can interactively draw displacement  
>> on your mesh).  Just thought I'd give you a heads up.
>> Tom M.
>> LetterRip
> I've now confirmed that what you want is ridiculously easy with my  
> EditMesh module, although there seems to be a few bugs (like for  
> example findnearestface doesn't like to be called repeatedly over and  
> over again).
> Right now I have almost completed full vert/face/edge support, and  
> plan to add bindings to the Subdivide functions, and whatever other  
> functions I think will be useful before I submit it to bf-python.
> joeedh
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
Ton Roosendaal  Blender Foundation ton at blender.org  

More information about the Bf-committers mailing list