Layer Control in Layouts & Thumbnail Update

rhino
mac
#23

Yes, I fully agree with that! Layer visibility should be completely separated between model and layout states.

Seems like they are considering the change, as you can see here
https://mcneel.myjetbrains.com/youtrack/issueMobile/RH-38476

1 Like

(Be) #24

First off, I would also love to have the ability to work with global/model layers and layout layers independently. That would ease the process when having multiple plan-drawings with lots of info on top of each other, and wanting to sift through different layers in the layout.

Second, I have a problem concerning the “Layout and detail information”. My detail view in layouts is constantly showing all layers, even when disabling different layers in the “layout and detail information” tab. The only action that effects the look of the layout is when i toggle the layer where the detail view is located - then the detail view disappears. But I am unable to change the visibility of the different layers from the “Layout and detail information” tab. Any ideas?

I hope this makes sense.
Thanks!

Ben

0 Likes

(Be) #25

Ah, I just realised that you need to have the detail view active for the “layout and detail information” layers to have any effect.
Sorry for the inconvenience.

1 Like

#26

I’m sorry with who don’t think so, but to me don’t have the possibility to hidden layers in model space independently from the layout space is merely an idiot thing. It means a lot more work. I think it is a background from the “Microsoft window style”: if you can do one thing with one click… do it with ten clicks. That’s my opinion. Roy

0 Likes

(Lahos) #27

I really wish to have an option to be sure my layout are safe… No matter which layers I turned on or off in model space.
Though, I think to have a global way to turn on/off layers for all detail at once is handy.
Suggestion : Would it be useful to have the detail lock option handling the model space layer state ?
If enabled only the layout layer state would be considered.

0 Likes

(Wim Dekeyser) #28

Is the Layer State Manager not doing that for you?

0 Likes

#29

Hi @wim,
The problem is that it doesn’t matter if you’ve used the layer state manager to configure your details, because as soon as you turn off any layer in model space, it will act as a global switch and will switch off that layer in any detail even if that layer is on in the detail. The only way to ensure that you don’t modify your saved layers configuration is turning every layer on in model space before printing your layouts.
This workflow is a real pain and very dangerous if you happen to work within a team, and someone else need to open a drawing to make some modifications and save that file forgetting to turn on all model layers.

I hope it makes sense and thanks for asking,

José

0 Likes

(Wim Dekeyser) #30

Hi José, yes that makes perfectly sense.
Perhaps one of the bigger brains has a firm grip on how to solve this issue, but, to me, there’s nothing that will make this process fool-proof - except (and certainly when working in teams) for tight work-flow control and good procedures.

Requiring that everybody in the team saves a layer state when a detail is finished, and then requiring that everybody restores the layer state before printing could be a good procedure and might even be scriptable.

But, remember that ,even if detail layers had a life on their own (which, as you stated further above, is on the wish list), if a user adds a new layer with a new object, this will be visible in every detail on all layouts. And, yes, layer states will not help here either.

0 Likes

(Lahos) #31

Hi,
I agree that layer state is really not a good solution. Too easy to mess up your work, even worse your team work (raised by José).
@wim I think the fact that a new object could come up in details is minor. I guess, a detail related option (like “locked” which concern only already existing details) could tell whether a new layer should be visible or not by default in layout space.

1 Like

(Wim Dekeyser) #32

All - Thanks for your input. I’ve bumped a YT issue that is more of an umbrella issue covering RH-38476. This wider one is only visible to developers though.

1 Like