Closed lfertig closed 4 years ago
Linked with RH3DM-55
First things first, I am new to contributing something here and assume people are fare more experienced with most matters. Hence I'm open to any guidance, (constructive) criticism and if someone feels this should rather be handled by someone else, please feel free to say so.
I had a moment to look at the python binding and would propose to store the ObjectIds in an std::vector
As for the conversion from ON_SimpeArray
I attached the two files of my minimal example: main.zip
I implemented this in my forked branch, making additions to bnd_instance.h/cpp and bnd_uuid.h/cpp. Maybe you can have a look at it when you find a moment, to see if this is how you would like it to be handled?
I tested it with various files of different complexity and different levels of nested blocks. You can recreate the .3dm block hierarchy in python using the new properties and function.
Closed via RH3DM-55
Instance definitions don't expose several attributes and methods. The 3 most important ones to provide basic functionality would probably be InstanceDefinition.Id, InstanceDefinition.Name and .GetObjectIds(), as listed in the .net docs: https://developer.rhino3d.com/api/RhinoCommon/html/T_Rhino_Geometry_InstanceDefinitionGeometry.htm.
forum thread: https://discourse.mcneel.com/t/rhino3dm-instancedefinitions/89904/5?u=fertig