Oh, okay then. So will implementing the
ChangeQueue give me an easy way to :
a) Access an individual mesh i.e a
CRhinoMeshObject or something similar, to get the mesh data, attributes.
b) Find out if the mesh is a part of the instance or not.
c) Easily map the mesh and the object/ block instance it belongs to?
I will be able to do all these, right? If so, I will gladly make the change to
So, the basic overview of my project is that I use
RhinoMeshObjects() to get an array of
Then, I use the
objectIterator to get all the objects on the document and store it in another array.
And, then I iterate the object array to search the mesh array according the id and then assign the mesh to the object.
(I do so because I am making another object definition for the software I am exporting to, so I am transferring the data of a Rhino object to another data container that contains all its data and the references to the mesh too from the mesh array I obtained earlier.)
So, what I am doing to associate the mesh to the object is by:
if (allMeshes[i].m_parent_object->Attributes().m_uuid == currentObjID)
allMeshes = the meshes array obtained from
currentObjID = the ID of the current object I got by iterating the object array obtained from
So, if implementing a
ChangeQueue will give me better organisation and won’t be much time consuming, I would really love to know that, Nathan.
Thank you, and I am awaiting for the sample code!