Data between Definitions - Grasshopper2024-03-29T11:38:56Zhttps://www.grasshopper3d.com/forum/topics/data-between-definitions?commentId=2985220%3AComment%3A1516707&feed=yes&xn_auth=noIndeed, you can quickly accid…tag:www.grasshopper3d.com,2016-04-26:2985220:Comment:15167072016-04-26T11:37:27.050ZAnders Holden Deleuranhttps://www.grasshopper3d.com/profile/AndersHoldenDeleuran
<p>Indeed, you can quickly accidentally break the declarative DAG-based logic which Grasshopper is based on this way. Tread carefully ;)</p>
<p>Indeed, you can quickly accidentally break the declarative DAG-based logic which Grasshopper is based on this way. Tread carefully ;)</p> You can also check out Treesl…tag:www.grasshopper3d.com,2016-04-22:2985220:Comment:15138522016-04-22T12:37:25.074ZDavid Stasiukhttps://www.grasshopper3d.com/profile/DavidStasiuk
<p>You can also check out <a href="http://www.bespokegeometry.com/2015/07/07/treesloth/" target="_blank">Treesloth's</a> Pack and Unpack components.</p>
<p>You can also check out <a href="http://www.bespokegeometry.com/2015/07/07/treesloth/" target="_blank">Treesloth's</a> Pack and Unpack components.</p> If you are interested in tran…tag:www.grasshopper3d.com,2016-04-22:2985220:Comment:15138412016-04-22T11:18:04.545ZChristian Kongsgaardhttps://www.grasshopper3d.com/profile/ChristianKongsgaard
<p>If you are interested in transferring geometry between GH scripts, Lunchbox has a component for that.</p>
<p>Slingshot could also be a solution.</p>
<p>Often I just write the data from one script into files and load them back into another GH script. Not super handy but it works fine.</p>
<p>If you use Ladybug/Honeybee, they also have components that can handle their data. </p>
<p>If you are interested in transferring geometry between GH scripts, Lunchbox has a component for that.</p>
<p>Slingshot could also be a solution.</p>
<p>Often I just write the data from one script into files and load them back into another GH script. Not super handy but it works fine.</p>
<p>If you use Ladybug/Honeybee, they also have components that can handle their data. </p> Look into Flux http://www.gra…tag:www.grasshopper3d.com,2016-04-22:2985220:Comment:15137432016-04-22T11:02:36.281ZDanny Boyeshttps://www.grasshopper3d.com/profile/DannyBoyes
<p>Look into Flux <a href="http://www.grasshopper3d.com/group/flux">http://www.grasshopper3d.com/group/flux</a> it was show cased at the GH User meeting in London last Monday. Looked promising! Also you are not restricted by location.</p>
<p>Look into Flux <a href="http://www.grasshopper3d.com/group/flux">http://www.grasshopper3d.com/group/flux</a> it was show cased at the GH User meeting in London last Monday. Looked promising! Also you are not restricted by location.</p> If it is within the same Rhin…tag:www.grasshopper3d.com,2016-04-22:2985220:Comment:15136452016-04-22T10:43:12.096ZAnders Holden Deleuranhttps://www.grasshopper3d.com/profile/AndersHoldenDeleuran
<p><em>If</em> it is within the same Rhino instance/session, using sticky is probably the easiest approach.</p>
<p><em>If</em> it is within the same Rhino instance/session, using sticky is probably the easiest approach.</p>