This shows you the differences between two versions of the page.
rhino:rhinov5status_layernames [2020/08/14] 127.0.0.1 external edit |
rhino:rhinov5status_layernames [2021/12/30] (current) dale |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Rhino 5 - Layer Names and Trees ====== | + | ====== Rhino - Layer Names and Trees ====== |
{{: | {{: | ||
- | Rhino 5 allows | + | Rhino allows |
Some Rhino users requested this ability to have sublayers with the same layer name to help them organize layers to make it easier to find similar small features in a large model. | Some Rhino users requested this ability to have sublayers with the same layer name to help them organize layers to make it easier to find similar small features in a large model. | ||
Other users have designed their work flows and parts libraries assuming that there are no duplicate layer names. If you are one of these users, the section below explains how you can configure Rhino so it will not create duplicate sublayers when importing models. | Other users have designed their work flows and parts libraries assuming that there are no duplicate layer names. If you are one of these users, the section below explains how you can configure Rhino so it will not create duplicate sublayers when importing models. | ||
- | |||
- | |||
==== Controlling layer names when importing files ==== | ==== Controlling layer names when importing files ==== | ||
- | For some users, having more than one layer with the same name disrupts their workflow. So Rhino 5 lets you control how layers are combined when Rhino imports an external model into an existing model. | + | For some users, having more than one layer with the same name disrupts their workflow. So Rhino lets you control how layers are combined when Rhino imports an external model into an existing model. |
**Note** There are many ways to //import// an external model into the existing model including: | **Note** There are many ways to //import// an external model into the existing model including: | ||
Line 36: | Line 34: | ||
===== Layer names in linked block definitions ===== | ===== Layer names in linked block definitions ===== | ||
{{ : | {{ : | ||
- | Rhino 5 has full support for linked block definitions. | + | Rhino has full support for linked block definitions. |
* **Active** All layers for the linked block definition are in the active model and are saved in the active model. | * **Active** All layers for the linked block definition are in the active model and are saved in the active model. | ||
* **Reference** The layer tree from the reference model is added to the active model as reference layers under a // | * **Reference** The layer tree from the reference model is added to the active model as reference layers under a // | ||
Line 46: | Line 44: | ||
You may download the files used in this example from {{: | You may download the files used in this example from {{: | ||
- | This example demonstrates the two ways Rhino 5 manages layer names for the contents of a linked block definition. | + | This example demonstrates the two ways Rhino manages layer names for the contents of a linked block definition. |
The model called // | The model called // | ||
Line 54: | Line 52: | ||
{{: | {{: | ||
- | |||
- | |||
- | Back to [[rhinov5status|Rhino 5 Status]]. |