EDIT2: The user is conditioned to expect Windows API dialogs (Options window, Worksession manager, Block manager) to prevent viewport operations. The Block Edit dialog (unlike the others of its kind) allows viewport operation and so it breaks consistency. The block edit dialog should be a floating dockable panel just like the UV Editor.
This wish relates to embedded blocks ONLY. (not linked) and recommends a simple rule:
“Keep parents as regular geometry within it’s source file”
a) If a file is linked as a block, the parent stays in the source file and only instances come in
b) If a block is merely embedded, so the source and host files are the same, then it stays as regular geometry while it’s being instanced within the file.
After many years using Rhino, blocks are still hard to use. Specifically, what gets me every time is that the parent block exists somewhere in memory invisible to the user. We delete all layers and all geometry and there is still invisible stuff in there and it’s cryptic how to bring them back (the Insert command is not in the manager and is not discoverable; should be named “BlockInsert”). If units change after the fact the definitions get out of scale sync. Block layer structure is no longer visible; a block with parts on multiple layers is hard to know which layers it occupies. Block insertion point if forgotten is messy to rediscover during an edit.
I WISH: →
a) once an object is turned into a block, this FIRST block should NOT be an instance, but it should be the parent block itself.
b) Rhino should have a way to notify the user that is a parent block and should be able to move it across layers like other objects.
c) If the user resizes or rotates this parent block, then all child instances should resize too.
d) The user should have a way to show/hide/edit the parent block bounding box and origin.
e) If the user deletes the parent block then the definition itself should be gone too.