When selecting a block instance, I really (really) need to see - immediately - on which layer the BlockDefinition resides. In R7. If modifying the definition there’s the risk of accidently moving the definition to some irrelevant Current layer and… well, I think people have had this wish a thousand…

[image] pascal: It feels more like we need a dedicated block management panel, I don’t think it’s better to create yet another panel to look for and click in order to see the info which should be shown together with all the other info we always keep an eye on. I think a property panel should…

[image] RIL: There is no confusion about what I am asking about Just because you are not confused about what you are asking, that doesn’t stop me being confused by what you are saying!

[image] RIL: the layer in which it was defined, I still think this is a misunderstanding or a jumbling of concepts - there is no such thing as a layer in which a block is defined; there are objects in a block definition and each of these objects resides on a layer. That’s it. -Pascal

What is the layer which cannot be deleted then? (due to a “block definition” being there, or associated with it)? That’s what I’m talking about, a real use case which happens in real life every time you try. // Rolf

Hi Rolf - that would be any and all layers which have objects that are used in a block definition. -Pascal

And why would you not want to show that layer info so that those layers (and associated blocks) can be known and thus managed? And converse, when selecting a layer, why not show which block definition (names) are associated with that layer so one can find and manage those blocks? It is a usecase t…

[image] pascal: that would be any and all layers which have objects that are used in a block definition. Here’s an example where that is not true: [image] Layers “Box1 DEF” and Box2 DEF (where I initially created the two boxes) are empty. Because I moved the instances from “Box1 DEF” to “…

[image] RIL: Layers “Box1 DEF” and Box2 DEF (where I initially created the two boxes) are empty. Because I moved the instances from “Box1 DEF” to “Box1 INSTANCE” (same for Box 2). Hi Rolf - this is the misunderstanding right here. What you moved are instances, the underlyng definition is not…

[image] pascal: What you moved are instances Yes, I explicitly stated that (to layer 3 & 4). Where did I NOT say that? [image] pascal: the underlyng definition is not changed in any way Can we actually use the word “definition”? It has been stressed here several times that there are n…

[image] RIL: [image] pascal: that would be any and all layers which have objects that are used in a block definition. Here’s an example where that is not true: -Pascal

Wish: LayerName of BlockDefinition Displayed in Property Panel

Rhino Rhino for Windows

Tom_P August 28, 2021, 3:58pm 49

I think it is very important to use a precise layer-structure when working with blocks:

Topic		Replies	Views
Change layer of block definition? Rhino for Mac	43	22279	July 7, 2025
V5 RS9 Layer Bug? Rhino for Windows	33	5042	July 23, 2014
Change layer of block definition? Rhino for Windows rhinocommon , python	38	11372	October 6, 2025
Block layer can't be changed Rhino for Mac	31	15793	September 21, 2016
There is a block definition on layer X, delete it before deleting layer Rhino for Windows	106	11386	September 26, 2019

Wish: LayerName of BlockDefinition Displayed in Property Panel

Related topics