I’m wondering about how the active layer functions.
Often, I want to hide the active layer, but an active layer cannot be hidden… So I have to make another layer active in order to hide that layer. If I have lots of layers that extend beyond my display, then I need to scroll far away to activate a layer with nothing on it, so I can hide said layer. Of course, I could just create an empty layer next to that working layer so I can toggle easily, but I think there must be a more intuitive way?
I guess it’s because objects are created on the active layer.
If you hide that layer and say draw a line, that line would be invisible.
So to avoid confusion (“Rhino is doing nothing!”) the active layer needs to be visible.
It is obviously an interface decision, not a logical necessity.
What I was trying to say is: McNeel decided to make it impossible to hide the active layer (there are valid reasons for AND against this). There are no technical reasons for it.
It’s valid that if a layer is active and hidden it may be confusing that nothing happens when you try to put something in the viewport! I think a simple warning box in this case would overcome this issue?
I agree, or make the current behavior the default setting (to accomodate and not confuse beginners) but add an “allow to hide current layer” check box in the settings to give experienced user the possibility.
You are not going to get any confirmation.
The tickets simply reflect the state to the best of our knowledge at any given point, and, yes, that changes all the time.
i completely understand, but having personal preferences might change the course of action, its never bad to hope for that! even if its very often futile
Since we are running a wish list…
I like that i can see the layer when i add something to it.
I am frustrated by having a selection of layers that are off to hide elements, but when i go to add something to a layer it turns on and stays on, so moving away from that layer leaves it on and have to click it off again.
Wish - when layers are selected Off, they stay off when moving to the layer or away from it.
When ‘working’ on an off layer it is visible and shows the ‘work’.
Hi Wim,
As i select for example ‘unfolded’ this becomes the active layer (Correctly) and automatically turns on with added items being visible.
When i go back to the DIM layer, the unfolded layer stays on, where i expect it to stay off as selected.
The working process is, go to ‘unfolded’ add, move do something, then go back to DIM and carry on, ‘unfolded’ stays off.
Another thing, to have many layers in various on off states looking to adjust. I sometimes flick down the list to see what pops up on which layer to find things, but then all the layers are on again.
I would like to see the layer state (on/off) separate from which layer is active at the time.
You could script this very easily. Like really really easily. You just need to decide which layer you end up on.
The script could search for an empty layer and put you on that one. Or just create a new layer and stick you on that new layer.
I’ve seen drawings destroyed in AutoCAD due to the active layer being turned off (and not frozen). I think something like this is better left for the user to customize rather than included in Rhino.
Hi Keith, that brings up the 2nd point of the ‘Lock’ i think this should also be ‘sticky’ active when working directly on the selected layer, but when you move to another layer the Bulb and Lock stay in the state that was originally selected.
Select in advance ‘Bulb/Lock’ state move to layer all is active, move away it stays as originally selected.
I have more than once edited accidentally an item because all things are selectable from anywhere unless you double check that the bulb/lock is activated again.
On 5-10 layers may not be a problem as they are all visible, but 100 layers…
