Overview of new and updated Grasshopper components

[michaelvollrath]

I imagine they are working on the documentation for the new components but in the mean time these are the most comprehensive coverages I have seen:

Original Overview:

Rhino 8 Feature: GH1 Is Now More Than Just Geometry!

New Data Types Available in GH1 Have you ever been frustrated that you couldn’t bake geometry with custom attributes? What about display materials? Have you ever wanted to be able to use native Rhino materials in the Grasshopper display pipeline? How about importing files into Grasshopper - have you ever become discouraged when you try to import a CAD file and lose all of the basic metadata that is included with the geometry? The latest Rhino 8 WIP now has new data types and components which e…

User Text, Custom Curve Display, ShrinkWrap:

Three new GH1 components in Rhino 8 WIP

User Text - This new component lets you add, modify, or delete user text (ie. key/value pairs) from model objects. Look for this under the Rhino tab and Object Attributes category. There are three different operating modes: Merge: When selected, the key/value pair(s) will be merged with the existing user text collection. If a key already exists in the collection, the value will be updated. Set: When selected, all existing user text items in the collection will be removed before setting the new…

Annotations & Hatches:

Rhino 8 Feature: Annotations and Hatches in GH1

New Annotation and Hatch Components for GH1 Have you ever needed to add dimensions, leaders, or text entities to your model to clarify an issue or enhance your documentation workflow? Moreover, have you ever needed greater control over the hatches you use in your models and/or drawings to really make them pop? Grasshopper 1 – in the Rhino 8 WIP – now has many new components which let you control annotations and hatches with ease. [AnnotationsHatchesToolbar3] Examples With the inclusion of s…

Recent Update Of Filtering Components:

Grouping, Sorting, and Filtering

Edited: 9/13/2023 The Problem with Filtering In the first post of this thread, I laid out some techniques for how to filter content based on a data type’s attribute or user text value. It worked, but with one major flaw. The Filter Content component had an input, called Key, which let you define what attribute or user text key that you wanted to use during the filtering operation. Because this was set on the Filter Content component itself, it meant that you could only ever use a single key dur…