Grasshopper

algorithmic modeling for Rhino

Dear All,

Grasshopper 0.9.0064 is now available for download from the usual location. This is a fairly minor update to 0.9.0062 which has the sequence selection pattern support that was used in last Wednesday's webinar.

New features:

  • Remap Component has been replaced by a new one with additional clipped output.

  • Floating Point parameters with coordinate data now have gumballs when selected.

  • Gumball and Meshing options were added to preferences, Viewport category.
  • Tree selector patterns (as used in Split Tree component) now supports sequence notation.

  • Split Tree component now also supports item index split logic.

--

David Rutten

david@mcneel.com

Seattle, WA

Views: 2903

Replies to This Discussion

Thank you!!

Is it possible to Pin this http://www.grasshopper3d.com/forum/topics/datatree-selection-rules so it does not get lost in the Discussions.

Hi grasshopper team,

thank you for your focus.

I recognized a major change of the Solid Difference Command. I am not sure if it is caused by Grasshopper or Rhino SR6. Up to now SDiff whiped every thing inside the B Solid, now just the Breps which are cutted by B. Is it a bug or a feature?

Norbert.

Thanks again David!
What does the Remap's Clipped output do?

Seems that the split tree component now requires curly brackets for the path mask while the previous version of the component did not.  

Is there any chance the previous version of the split tree component could continue to be supported using the "old" convention?  Not looking forward to replacing hundreds of split tree components...

It worked before without any brackets? Or did you have different brackets?

I don't want to make it work as ambiguously as before, tightening up and unifying the notation for this sort of thing is an important part of continued GH development.

But there may be another solution. Are you generating the splitting masks through logic or have you typed them all in by hand in a text panel or directly in the Split Tree input?

--

David Rutten

david@mcneel.com

I have been using no brackets.  Made it a tiny bit simpler to build branches from integers and strings.

I use the split tree component both where I build the path with logic and where the input is static from a text panel.  

What Danny writes makes sense to me. Any chance there is a 0.9.0062 install available to use while updated the split trees?

I attached a VB script which shows a window with a button that attempts to fix panels hooked up to Split Tree components.

If a panel has no inputs, only plugs into Split Tree components and has usertext that doesn't already have curly brackets it will add them. Does this go someway towards automating your files?

--

David Rutten

david@mcneel.com

Attachments:

It will definitely fix some instances, thanks!

If you have another common case, I can try and adapt the script to cater for those.

I attached a better version of the script, now the button works on whatever file is open rather than the file from which it was created.

--

David Rutten

david@mcneel.com

Attachments:

I just saw the updated response, thanks again for your help!

I think that this is a breaking change with no way to support both.

http://www.grasshopper3d.com/forum/topics/datatree-selection-rules

Braces or "Curly Brackets" {} are used for Paths,

"Square Brackets" [] are used for Indices

Parentheses or "Round Brackets" () are used for grouping rules within the other types.

"Angled Brackets" <> are not to be used as these are reserved for Less Than and Greater Than

Therefore when GH has to parse a text string like "{0;0;(4 to 8)}[(1 to 4) OR (7,9,...,18)]" there can be no ambiguity.

A simple example of (0;0;1) might be obvious that it should be a path mask falls outside the new rules  

Attached is a UserComponent that will convert Parentheses in a Text String to Braces. It won't do them all by automatic but you can pass the mask through it to save editing each one. If you have the mask in the component input, right click and extract parameter and then pass it through the Par2Bra component.

Attachments:

Thanks Danny!  What you write makes sense -- I have started updated scripts using a similar method.  I will try your converter as well.

I missed that thread on the split tree change, if I had seen it I could have take care of this before updating!  

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service