This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Previous revision | ||
rhino:rhinov5status_layernames [2015/09/14] |
rhino:rhinov5status_layernames [2021/12/30] (current) dale |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Rhino - Layer Names and Trees ====== | ||
+ | {{: | ||
+ | |||
+ | Rhino allows layer names to be repeated if the repeated layer names are sublayers of different layers in the layer tree, as shown in the example above. | ||
+ | |||
+ | 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. | ||
+ | |||
+ | |||
+ | ==== Controlling layer names when importing files ==== | ||
+ | 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: | ||
+ | * Use the Import command | ||
+ | * Use the Paste command | ||
+ | * Use the Insert command to insert a file as a group or as objects | ||
+ | * Use the Insert command to insert a linked block with reference layers as a group or as objects | ||
+ | |||
+ | The **Rhino Options > Files** tab in the **Options** command dialog offers two options for managing layer names. | ||
+ | * **Use complete layer tree from source file** Rhino will create a copy of the imported model' | ||
+ | * **Use existing layers with matching name** If a layer in the existing model has the same short name as a layer in the external model, Rhino will add everything on the external layer to the existing layer. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== Example ==== | ||
+ | |||
+ | Below is an example that shows what happens when you open a model named // | ||
+ | |||
+ | You may download the files used in this example from {{: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ===== Layer names in 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. | ||
+ | * **Reference** The layer tree from the reference model is added to the active model as reference layers under a // | ||
+ | * This image shows where you specify the linked block definition layer style when creating a linked block. | ||
+ | |||
+ | |||
+ | |||
+ | ==== Example ==== | ||
+ | You may download the files used in this example from {{: | ||
+ | |||
+ | This example demonstrates the two ways Rhino manages layer names for the contents of a linked block definition. | ||
+ | |||
+ | The model called // | ||
+ | |||
+ | {{: | ||
+ | |||
+ | {{: | ||