Referencing 3dm files - layer filter

I like to reference 3dm files and create something like an assembly.

The reference 3dm component has a layer filter, but what if I forgot how all the layers in my referenced files are named? Is there a way to create a layer table of a referenced 3dm file?

When connecting a value list to fabtools text component font input, you automatically get a value list with all the fonts available. I wish to have the same option when referencing 3dm files.

Replies to This Discussion

Permalink Reply by Pieter Segeren on August 17, 2015 at 1:49am

Hi Martin,
Human has a component called LayerTable that returns all layer names (and child layer names too) in the rhino file.

Permalink Reply by FRiou on August 17, 2015 at 1:50am

Hello Martin,

I know the Human plugin has a Layer Table component. I've never used it so I don't know how it works, but maybe it can help in your situation ?

Permalink Reply by Martin Siegrist on August 17, 2015 at 2:12am

I'm looking for a layer table of a referenced 3dm file, not the active rhino file...

Permalink Reply by Pieter Segeren on August 17, 2015 at 2:43am

Ah, hmm, sorry for misreading that. The (Rhino.FileIO.) File3dm type has a Layers property, you could tap into that.

Permalink Reply by djordje on August 17, 2015 at 2:52am

This is the example Pieter mentioned.

It requires ghpython plugin installed.

Attachments:

3dm_layers.gh, 11 KB

Permalink Reply by Martin Siegrist on August 17, 2015 at 3:45am

Perfect. I think I need to learn more python! Thanks

Permalink Reply by Martin Siegrist on October 26, 2015 at 1:34pm

Actually, I just realized Rhino.FileIO layer creates a layer list with no information whether one of the layers is a sublayer.

Any ideas how to create full layer names?

Permalink Reply by djordje on October 26, 2015 at 2:13pm

Hi Martin.

By "create full layer names" you mean path of the layer ("Layer 02::subLayer02::subSubLayer02)?

In theory you just need to call the "FullPath" property, but for some reason it does not work. I will attach the file so that Giulio or somebody else could tell us why it does not work properly.

Attachments:

3dm_layers2.gh, 11 KB

Permalink Reply by Martin Siegrist on October 26, 2015 at 2:28pm

Yes, I meant full path.

Looking at the Import 3DM component, it does not support full paths either.

When referencing files, I think it would make sense to have the opportunity to use full path layer names as layer filters. Otherwise you'd need to name sublayers ?bijective?

RSS