In both these cases the problem stems from a flat data model in Grasshopper. You are looking to take multiple lines and divide them into a number of points, then you would like to address the points indexed to the curves they came from. This is something the Grasshopper data structures do not deal well with and is exactly what David is currently working on. See:
http://groups.google.com/group/grasshopper3d/browse_thread/thread/5e804f0b511b505c# Until we can get our hands on the new technology I have seen this problem dealt with in two ways. 1) You need to fix the number of curves you are using as inputs. This way you can create a true/false cull pattern to extract the points you want. on each curve. Then puch those extracted points downstream. 2) The second way is through a VB component. Here you can sort the points. But with a fixed number of outputs on the VB component, you probably will still need to do much of the drawing work in the script itself. This can be quite a task if you are new to VB.NET. I have not seen Damien's script, where is it posted? I understand your frustration with the VB.NET documentation. It can be a real bear. We are also working on that. Rajaa and I are working on some tutorials that may be helpful. You can see some of the work here: http://en.wiki.mcneel.com/default.aspx/McNeel/GrassHopperWorkshop.html I will work on a fixed number of lines version to show you one example that may work for you. On Jan 23, 6:06 am, dingle <[email protected]> wrote:
