Formatting input for Relative Item

Replies to This Discussion

Permalink Reply by mark zirinsky on January 14, 2016 at 7:06pm

the {} numbers are the path, and the [] are the index. a useful component is 'tree statistics' , which will give you a path list, this can be used as an input for a tree item. 

Permalink Reply by Ethan Gross on January 14, 2016 at 7:31pm

Thank you Mark but I am interested in the actual mechanics of character manipulation in order to compose the statement above. The component tool-tips in the Text menu are not exactly self-explanatory. Though naturally lazy, I searched and there are not a lot of examples floating out there for formatting in general; maybe it's just me...

Permalink Reply by mark zirinsky on January 14, 2016 at 9:41pm

you can compose the text by inputting a number sequence, from the number component, into a txt component. it will convert to text for you, then try feeding that to the relative path.

also, you might like this discussion:

http://www.grasshopper3d.com/forum/topics/lists-sets-strings-trees

and

http://www.grasshopper3d.com/forum/topics/relative-item-component-b...

Permalink Reply by peter fotiadis on January 14, 2016 at 11:47pm

Get these as well as a "guideline". Notify if you need far more complex rel-items examples (or split tree).

Attachments:

• POINTS_VS_GRIDS_V2.gh, 160 KB
• Points_and_then_some_V1.gh, 108 KB

Permalink Reply by Ethan Gross on January 15, 2016 at 12:21am

Thank you Peter. I wish I knew about these methods much earlier - and I even managed to find the answer to my question amongst the treasure trove!

Permalink Reply by peter fotiadis on January 15, 2016 at 1:22am

Well rel-item(s) is rather very simple: imagine cloning a tree: on the left you have the OEM, on the right the clone (with the shifted indices with regard branches and/or items) . So you pick one thing from the left and another from the right and do business.

The equivalent via the Dark Side is:

Point3d p1 = SomeTree1.Branch(i1,i2,i3, ...)[j1];

Point3d p2 = SomeTree2.Branch(k1,k2,k3 + shift1 ,...)[j2 + shift2];

If you are really brave see this attached as well (requires a triple espresso [min]). If you can master this ... there's nothing that can stop you (but the Dark Side better IS, he he).

Attachments:

• twist_and_go_V2.gh, 187 KB

Permalink Reply by Ethan Gross on January 15, 2016 at 2:23am

A triple espresso, a seven percent solution, and a bed of nails. Thanks.

Permalink Reply by peter fotiadis on January 15, 2016 at 2:42am

The only way the hard way IS.