<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1106" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#d8d0c8>
<DIV><FONT face=Arial size=2>Hello it's me joseph again.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I have come down with some sort of plague today.
(Cough.. cough...) Anway, I made the the needed changes to the vertex group
stuff in object.c. It now has the following:</FONT></DIV>
<DIV><FONT face=Arial><FONT size=2><FONT face=Arial
size=2></FONT></FONT></FONT> </DIV><FONT size=2>
<DIV><FONT face=Arial>@selectVertexGroup(name) - selects vertex group based on
'name'</FONT></DIV>
<DIV><FONT face=Arial>@deselectVertexGroup(name) - deselects group</FONT></DIV>
<DIV><FONT face=Arial>@addVertexGroup(name) - adds a new group to object by
name</FONT></DIV>
<DIV><FONT face=Arial>@removeVertexGroup(name) - removes a group by
name</FONT></DIV>
<DIV><FONT face=Arial>@assignVertexToGroup(vertexList, group, weight,
assignmode) - takes a python list of vertex point indeces, groupname, weight,
assignmode. This function should not be called though until all mverts are in
the mesh because it creates a new array of size(mverts) if no dverts are
detected.</FONT></DIV>
<DIV><FONT face=Arial>@removeVertexFromGroup(group, vertexList) - takes a group
and a python list of vertex points (optional), the group name alone will
remove all</FONT></DIV>
<DIV><FONT face=Arial>@returnVertexFromGroup(group, vertexList) - takes a group
and a python list of vertex points (optional), the group name alone will return
all. Data is </FONT><FONT face=Arial>returned as a python list
corresponding to [(x,y,z,index),(x,y,z,index),etc..]. If the vertexList contains
indeces not part of the group passed no data is returned in the list for it,
which could be used as a test for whether a vertex is in a group.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Try it, you'll like it :)</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Attached is the object files, and a script to do
selections on a UVSphere. (before this was pretty slow - but i fixed
that). Also I threw some definitions into the .py file (just in
case).</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I have tested it on primatives but not on a scripted
importer, that's my only concern. I don't see any reason why they wouldn't work
though on 1 and not the other.. </FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>So I know that this is not the best place for some of this
stuff. The assignVertexToGroup, removeVertexFromGroup, returnVertexFromGroup,
would probably be better in NMesh, however, that would require getting a pointer
to the object that owns the mesh data. Also, assignVertexToGroup will create a
new dvert mesh matching the mvert mesh in the mesh data, so it might be more
intuitive to create the mesh, link it and then select vertex points from the
mesh to add to groups. One of the reasons i thought that returning data is good
is both for testing vertex/group associations and also because most file exports
might need to know that stuff.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>So, in conclusion, if my rambling post makes little sense
it's because im sick. </FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>Joseph</FONT></DIV>
<DIV><FONT
face=Arial> </FONT></DIV></FONT></BODY></HTML>