[Bf-python] Vertex Influence for no-armatured objs

[Willian Padovani Germano]

Hi,

From: <models at paposo.com>
(...)
> My only
> suggestion is that the EMesh not be an object/mesh IN editmode, because
some
> vertex group stuff depends of the fact that your not in editmode.

** Which stuff, exactly?  We need to know that to decide if EMesh can really
handle it all or if we do have to use Object for something and simply live
with that, because that's how Blender works.

If you mean things like selecting all verts from a vgroup, then we can make
it an optional argument to EMesh.GetFromObject("objname"), like:
EMesh.GetFromObject("objname", "vgroupname1", "vgroupname2", etc)

so that we already get and editmesh with these verts selected.  We can even
be fancy and do booleans on these groups: select all verts from vgroup1 and
vgroup2, except those in vgroup3:

EMesh.GetFromObject("objname", "vgroup1", "vgroup2", "!vgroup3"), if there's
a need for this.

> That's one of the reasons i think that returning a data-specific object
> could be useful once linked.
(...)
> good idea/bad idea??

Let's investigate a little more and see if we really can't solve this first
issue in EMesh.  Possibly we can go on without an extra layer.  Even if in
the end Object must be wrapped as it is, with specific data here and there,
the methods will still only work for their right types and give an error
otherwise, so that's not so bad.

One thing, though: EMesh must deal with editmeshes, really, because only
these have info about selected verts, faces, and that's what we need to add
to the mesh API.

--
Willian, wgermano at ig.com.br