For a less politically comment about Blockedit (Mitch, cover your ears !) :
This essential tool’s UI is still the same shameless hack as it was when it was introduced, maybe 20 years back or more ! I mean, all it’s doing is tricking the user into thinking we’re actually in a “sub-space” of the model, when it’s just a cosmetic shuffle of locked states. This becomes apparent AND VERY DANGEROUS if you use the “Unlock” tool within this context because EVERYTHING in the model becomes unlocked. Then, you can be fooled into thinking you are back in your model, screwing up you blocks, and wreaking havoc on your model’s block structure.
There’s so many unpractical, unhelpfull, lazy things going on in this Blockedit UI, and many of us have complained about them endlessly in vain, but this carelessness with locked objects is the best giveaway that McNeel still doesn’t take the blocks seriously.
Please tell me that the only improvements to Blocks in Rhino 9 will not be the export of user data.
I wouldn’t even call that a low hanging fruit. It’s fallen from the tree and rotten already, meaning “super simple yet wayyyyy overdue”.
We really need to see a more structured display of block…structure in that Block edit UI.
Like, creating branches when a sub-block is present multiple times, allowing “reverse highligh” (when an instance is selected in 3D, select the said instance in the Blockmanager block list).
Maybe I sound like a grumpy old fart, but really, you guys have been negligent with all this stuff and deserve taking a bit of heat !
The BlockEdit code is being rewritten to get rid of all old bugs that have both caused problems for users and that have prevented new things to be added. Fixing the foundation is not something that will show itself in the UI but is a very necessary first step.
Showing the tree structure is a very old request indeed.
→ RH-9136 Block Tree Structure
-wim
