Block Instances and Locked Objects - Counterintuitive

Rhino Rhino for Windows
1

I have been working with some blocks lately and I came across some very annoying, frustrating and counterintuitive behavior regarding blocks inside Rhino, specifically related to locking layers.

What I often do as best practice when working with blocks is, with layers, separate the original geometry inside blocks from the instances of said blocks.

image

Now, what I have noticed is that if I lock my BLOCK GEOMETRY like so:

image

All block instances (despite not being locked) become locked too!

Screenshot 2024-10-03 172617
Screenshot 2024-10-03 1726171920×840 159 KB

I should definitely be able to move instances around despite the geometry inside of it being locked. An instance is a separate individual object.

File here: BLOCKS FILE.3dm (268.6 KB)

What is funny, is that if I lock all layers except one like so:
image

I can still select the locked geometry! (WHICH MAKES SENSE BTW, JUST THAT IT SHOULD ALSO WORK IF ALL THREE LAYERS (01, 02 AND 03) ARE LOCKED.

image
image1920×1013 197 KB

1 Like
2

hmmm this is interesting. :face_with_monocle: :thinking:

It would probably be alot easier if Rhino would just adopt the whole components and assemblies ideologies of the other CAD’s. Relying on ‘blocks’ for this is kinda just beating around the bush imo.

Components and assemblies would be sweet cause you could import a component and just anchor it to a particular geometric entity and move it around or somem.