Stumbling (Through) Blocks

Quoting @AIW

"…

It’s important to realize that there is a difference between a block definition and a block instance.

One of the inherent stumbling points for users new to Rhino’s blocks is that a definition can show up in a model masquerading as an instance (one object serving both roles). Eventually after sufficient headaches, users tumble onto a practical way of dealing with the confusion this causes: they adopt a disciplined way of separating the two functions. That’s what the suggestions here are based on. It starts with the user’s mental model of the block system having these two functions and that it is up to him/her to keep them separate for the sake of organizational sanity.

Could the developers have built this discipline into Rhino at the start? Yes, but they didn’t - mostly (IMHO) because they themselves didn’t at the time recognize the importance of keeping them separate.

…"

I don’t remember this confusion with AutoCAD 25 years ago, but, in all fairness, I wasn’t doing drawings on the same level that I do now! AutoCAD Layer 0 seemed magical to me.

Could there be changes to how Rhino handles blocks? Probably.

Learning to understand and deal with the quirky behavior of blocks is a good start for me.