[Plugin][WIP] Layers Panel - Behaviour
-
-
Another question posted in the dev topic :
Layer colors
We cannot retreive layer colors from the api, so I won't be able to sync them with the plugin. TIG wrote a workaround to define a layer color by RGB values, but not a material. So that'll be a big limitation of Layers Panel. I personally never use layers color, so I need people to tell me if that's a needed feature, and if they want me to include TIG's code.
So, to summarize :- What's possible : Set a layer color, but only color
- What's NOT possible : Get existing layer color and display them in the plugin window. Set a material to a layer. And if a color is set by the plugin, it cannot detect change if color is changed in SU's layer window.
-
Layer0
Do you want to be able to sort and nest the Layer0 like any other layer ? Currently, I made it to stay at the stop, but I can make an option for that if people want to, so you would be able to choose Layer0 behaviour.
-
@jiminy-billy-bob said:
Hi !
But what if you have 1 child layer assigned to 2 child groups nested in 2 different parent groups ? Like this :
-
ParentGroup1 (ParentLayer1)
-
ChildGroup1-1 (ChildLayer1-1)* ChildGroup1-2 (ChildLayer1-2)* ChildGroup1-3 (ChildLayer1-3)
-
ParentGroup2 (ParentLayer2)
-
ChildGroup2-1 (ChildLayer2-1)* ChildGroup2-2 (ChildLayer1-2)* ChildGroup2-3 (ChildLayer2-3)
Then if you hide ParentLayer1, all of its children are hidden too : ChildLayer1-1, ChildLayer1-2, ChildLayer1-3. Then you get this (Italic is hidden
-
*ParentGroup1 (ParentLayer1)
-
ChildGroup1-1 (ChildLayer1-1)* ChildGroup1-2 (ChildLayer1-2)* ChildGroup1-3 (ChildLayer1-3)*
-
ParentGroup2 (ParentLayer2)
-
ChildGroup2-1 (ChildLayer2-1)* ChildGroup2-2 (ChildLayer1-2)* ChildGroup2-3 (ChildLayer2-3)
Well, that's a problem, ain't it ?
The only way (that I know of) to assign a comp/group to 2 different layers, regardless of nesting, is to assign the comp/group to one layer and its internal raw geometry to another layer.
This is a "best practices" NO-NO.
ALL RAW geometry should reside on layer0. Only comps and groups should be assigned to other layers.
There are a few exceptions for specific purposes, such as descriptive labels, documentation or dimensions contained within the comp/group. In that case you can turn on/off descriptions, doc and dims by assigning all such labels to a single separate, but common layer.
Then they will be visible only if the comp/group layer is visible.There are a few other reasons as well, but great care needs to be taken, or other stuff just disappears when hiding layers.
So, in answer to your question, it may only be a problem if you assign a layer to raw geometry.
So yes, I would like to be able to nest layers within other layers, not just layer groups.
-
-
@jiminy-billy-bob said:
Layer0
Do you want to be able to sort and nest the Layer0 like any other layer ? Currently, I made it to stay at the stop, but I can make an option for that if people want to, so you would be able to choose Layer0 behaviour.
NO
Layer0 should remain status-quo."Best Practices" say that layer0 is ALWAYS the current layer, and ALL raw geometry is assigned to it.
Then you comp or group geometry to keep stuff separate, and assign layers to comps/groups only, to control visibility.I learned that the hard way in the beginning of my SU experience.
Advertisement