Sticky id about digitalcircularitytoolkit

[soerensenkarl]

I've started with a solid csv reader, as I think that is the most important and should be an option if the livelink falters anyway. I'm making it so it reads a sheet that's organized like the attached with an id per unique geometry, it's dimensions and quantity. The component then outputs GH_Geo for every item, as well as its id and dimensions. This geo can then be fed into your object components for further manipulation.

[keithjlee]

Cool, looking forward to it.

If we work with IDs, it needs to come from upstream of Grasshopper, as there is no persistent data in GH. IE if the Object component generates an ID for each input geometry, when you close and reopen the script, it won't be the same IDs.

In Rhino, however, you can get unique IDs. That's how I handled updating the geometry to the solved positions in FDMremote.