V8, GH1, Rhino toolbar

Grasshopper
1

Every time I use the new toolbar I am struggling.
I think I have been reporting this before. Why is Rhino reading everything when layer filter is applied? Human shows none and this is correct response.

image
image1650×793 82.4 KB

2

Hi Piotr,

That input is pretty much superfluous, it will bring in a layer from another file, not filter. Please see this recent youtrack for additional details.

3

The Rhino 8 version of this reader works differently at the moment. It is not really an reader and an Objects filter.

Each of the inputs excluding the first two (File and Name) are actually object tables, not object elements in Rhino. Layer Definition, Linetype Style, Hatch Pattern, Annotation Style, Material Definition and Block Definition. So, the input to each will filter for that definition that is defined in a table, but does not necessarily exist as an object on the screen.

So in the case above the importer will return the Layer Definition called Block.

Using a Filter after import is the only way to filter out the geometric objects at this time:

image
image1484×650 88.9 KB

4

I don’t understand it.
How come it is not working here? It is an exact copy of your solution.

image
image1691×1139 105 KB

Human wins, again.

5

This is a bit different in Rhino 8. Partially because this is inside the Rhino doc there is a lot of options.

In this case using the right search key is the trick. I can see how this is not super clear.

image
image1101×883 75 KB

Searching on Layer keys there are 3 built-in keys that might be of interest:

For instance in the example the Layer is Openings::Glass

  1. Layer.Name - Glass - The simple name of the layer.
  2. Layer.Parent - Opening - All the parent path to the layer. Would include :: if there are miltiple parents.
  3. Layer.Path - Path is the full parent and name to the layer: Openings::Glass. This is what would work in the example you have also.

I am not sure there is anything wrong here, but it clearly needs to be documented what all these built-in keys mean…

6

Hi Scott
I am going insane over this example.
I have switched the Key to the Model Layer and tested it with: Path, Parent and Name (for full and short names)- still nothing appears at the right panel:

image
image1423×1072 75.4 KB

What am I doing wrong here?

Some more problems I can observe:

  1. It still displays the content even when the import is set to False.
  2. I have tried to filter the layer content in various ways - it either displays everything or nothing.
    image
    image2515×1519 383 KB
7

Can you send me the model and defintinion? I will look at it right away. You can PM it to me if you do no want it public.

I am also confused why it is not working at this point. Layer.Path is what the Key should be, but I can look closer.

8

So here is what is happening. I can see why it is run this way, but not exactly sure it has to be this way or not. We will look at the code.

The key needs to be Model Object.Layer.Name . Currently the Key is set to Model Layer.Name. So it is looking to filter the layers itself and not the Objects within the model.

Here is setting the 3 keys:

  1. Model Object.Layer.Name
  2. Model Object.Layer.Parent
  3. Model Object.Layer.Path

image
image883×372 47.4 KB

Here is the key selection menu:
image

9

Oh boy!
I get it working now, but I would never guess I need to look for Objects being connected to the objects - it’s duplicating the effort and confusing.
I sort-of understand why it’s been built this way and, once I know how it works, I’m going to use it extensively.
The other thing I would try to improve is the selector menu itself. When options are expanded they need to become bold or other greyed out as you can scroll too far and run to Name or Parent of different properties.
Thanks for your patience.
P