the mapper would be {A;B;C;D} and as your list of numbers changes in the 3rd row the output letter would be (C)
so would look like this.... {A;B;C;D} (i) > {i} (C)
Matt…
Added by Matt Gaydon at 11:09am on February 19, 2010
989e-044e8580d9cf"; //this is the grasshopper GUIDplugin = rhino.GetPlugInObject(pluginId, pluginId); // rhino is a COM object representing a rhino5 instanceplugin.OpenDocument("D:\MANUEL\Desktop\debugging.gh");
when running the OpenDocument method a window pops up with the following message
Grasshopper breakpointInvalid parsing operation inn GH_DigitNumber.Value
Running equivalent code in the RhinoPythonEditor works well.Please note that "plugin" in the code is an instance of "GH_RhinoScriptInterface" from the graashopper API.
Thanks.Manuel…
le data bundle to hand it to hoopsnake (using the entwine - and tree explode command) Now I am facing a big Problem: Hoopsnake somehow doesn't accept and process the tree structure in the D* input correctly. As you can see in the picture below, the output "A" shows a structure of {0;0} N = 3 {0;1} N = 3 but the mouseover on the input "D*" in hoopsnake shows a different structure {0;0} N = 4 {0;1} N = 2 There are no commands or anything inbetween. Has anyone of you faced similar issues and maybe knows how to deal with it??? Is it a bug or am I doing something wrong? Any help would be greatly appreciated Cheers, Benjamin Edit:btw, the problem also occurs when i don't use the data delay command. So that's not the problem …
001} (list of data D)
{002} (list of data E)
{01} (list of data F)
{010} (list of data G )
{011} (list of data H)
/==C
/==B |==D
==A \==E
\==F |==G
\==H
If you merge a list with path {0}, another with {0;0} and another with {0;0;0}, what you get is a tree with three branches, you actually will not join those lists, only they will placed in the same tree. In this case to join the three lists, you have to do is flatten all to {0}, then when they come together, as they all have the same path ({0}), the data will hang in the same branch/list, as if {0} were the trunk.
Some components automatically append elements to the paths with the idea of "hey! I've been here," so we get things like {0;0;0;0;0;0...}, GH prefer to give that information, but often it is irrelevant, and can be simplified to {0} with the simplify option in the parameter menu.
All lists in GH are actually a branch of a tree, although we can call it lists if the data structure has only one branch. So! {0} and {0;0} are different paths and if you flatten, all branches become {0} and data from all branches will gather if you put them together.
{0}(Lists A,B,C,D,E,F,G,H)
==A,B,C,D,E,F,G,H…