A question about layers
-
Could someone please clarify a couple of queries I have about layers?
I have a component which is made up of 2 sub-components.
When I created the component I had 2 different layers in the scene. One was called 'Cabinet', the other called 'hidden'.
I made the component so that one of the sub-components is on the 'hidden' layer, the other on the 'cabinet' layer. (The final 'parent' component is also on the 'cabinet' layer.)
The idea was that when the 'Parent' component is placed in a new scene with only the default layer0, it creates the 2 new layers ('cabinets' and 'hidden') and puts the the parent and one sub-component on the 'cabinets' layer and the second sub-component on the 'hidden' layer.
Here is the issue I am having and a couple of questions:
When I place the component, the parent is placed on the default 'layer0', not as needed on the 'cabinets' layer. Why?
One solution is to create the layer 'cabinets' in the empty scene before placing the component, select that layer and then place the component. Question; I have seen various posts in which the recommendation is not to place components in a secondary layer, but to place them in the default layer0 then move them. Why? Is there a logic behind this?
Alternatively I could place the component on the default layer0, then while it is selected use the 'Entity Info' dialogue to move it, but this requires the Entity info to be opened each time a component is placed, or to be left open and take up screen space.
I could place the component on Layer0 then use the 'Move to Layer' ruby to move it. The problem is that this ruby moves the parent and ALL the sub-components to the cabinets layer - which I don't want.
Sorry to labour the topic, but I just wanted to clarify all the options as I understand them and to also ask if there is another alternative to those I mentioned that I am not aware of
-
hi peweuk,
it is always easier to understand groups/components and layers, if you imagine them as physical objects.
with the example of your question, why the component isn't on the cabinet layer...just imagine a component is a box. so you have a big box and two smaller boxes within (these boxes contain the raw geometry - edges and faces).
now you 'paint' one of the small boxes with the 'hidden-layer' and the other with the 'cabinet-layer'. and all of this happened within the big box (the parent component)
next you 'paint' the outer box with the 'cabinet-layer'. but that is like going into a store, taking a box with toys off the shelf and covering it in nice green painting. this one box may be green, but that doesn't affect the other boxes at all - the painting was applied outside the box.
so to come back to your component: you applied the 'cabinet-layer' to the component. but that doesn't affect a fresh copy of it from the shelf (the component browser).was that comprehensible?
but to be honest, I am not sure what you need the parent component to be on a layer for. if you switch off the 'cabinet-layer' the first sub component vanishes. if you switch off the 'hidden-layer' the second sub component vanishes. and because the whole content of the parent component is hidden, you can't select it anymore (as if it was hidden itself).
but if you really need the configuration with the parent component being on a layer as well, either use the entity info to place it manually or create another component around the parent component (within this additional box the layer-information of the parent component will be saved) and explode it after placing it in the scene.
to your question about people mentioning always to do things on layer0 and then moving it:
that is about modeling on layer0, then grouping it and then putting the groups/components on layers. the reason is that if you don't do that it may happen that one group is on layer-A, but the edges and faces within the group are on a different layer. that can be very confusing and cause a lot of problems (e.g. if you accidentally drew the geometry of the roof on layer walls: when you switch off the 'roof-layer' the roof vanishes all right. but if you switch off the 'walls-layer' the geometry within the roof group vanishes as well).so always make sure that the raw geometry is on layer0. you can do with groups and components whatever you want. thus you are on the save side and it is easier to keep your models clean.
I hope that helped you to understand grouping and layering in SU a bit.
-
Thanks Guys.
I think now I know how to deal with my component/layer issue.
I have created a 'template' that has the layers already set up, and will select the 'cabinet' layer before placing the component from the library. As the subcomponents are all allocated to layers, this will not cause any problems/confusion regarding the various parts.
@unknownuser said:
but to be honest, I am not sure what you need the parent component to be on a layer for.
The answer is quite simple. I produce a cutting list, and prior to running it the components for which a cutting list is required have to be selected first - ie the cabinets only. So I use a 'Select by layer' script to select only the components in the 'cabinets' layer. However this does not work if the 'parent' is on layer0 as the select by layer ignores it and all sub-components of it, unless it is on 'cabinets' layer.
Thanks again.
-
So,
Ref; Default layer zero;
It's a greedy DEFAULT layer that you cannot delete ... zero cannot delete anything, or move its contents into your current layer.
Solution; -
Keep the 'entity info' window where you can see her. (Always! ... not unlike 'properties' in AutoCAD)
Ditto layers window. Again, always there.
So:
Go to your model; define components by select-dragging top left to bottom right over just one component.
Go to your newly opened 'entity-info' window and click on the drop-down arrow, by layer, and choose the (appropriate) layer, (Not Zero,) With each. If in doubt - go to Layers and type in an 'add' to make a descriptive layer. You'll see what we mean when you get there.
But just in case it's even more complicated ... maybe you have inherent components that are not entirely sure which layer they belong;
If you don't mind exploding and re-componenting (although expensive on file size,) the ultimate fail-safe is to have absolutely everything in the layer you want; if its got confused; 'explode' and re-layer.
Anyway, ref your question; Is there logic re secondary layer ... yes.
Advertisement