eobet
March 2, 2020, 8:53am
9
Boy, do I feel left out…
Yes. Yet . Another . Thread . On . This . Matter .
Annoyance 327:
Isolate block instance
Edit block instance
Select object within block instance
Hide that object
Show objects
Result: All objects are now visible, even objects outside of the instance. I now have to stop editing the block, and start all above steps over again, in order to edit the next nested part.
Expected: Only objects in the block currently being edited should be shown.
(I’ve had the above happen with isolate/unisolate as well, …
So this thread is the inverse of this thread .
If I right-click a layer and choose “select objects”, I get “No objects added to selection”, yet when I try to delete that layer, I get this:
[image]
(Note that I don’t get the block definition warning from the previous thread due to the following script .)
So apparently there are objects within a block definition that reside on this layer (while the block definition AND instances resides on different layers), but I have 700+ blocks in this file, …
Ok, so first, there are many , many , many , many problems with editing blocks. But apparently it’s all fine because it’s been like this for 20 years, so no need to change, right?
What are these and how can I get rid of them?
No, I can’t share the file, so let me describe:
It looks as when you are editing a block instance and everything else turns dark grey. Only, these objects are outside of any instance.
They’re on a layer, though, because when I hide one particular layer, they disappear…
Why do all (STEP file imported) nested blocks appear duplicated on top of each other when you try to edit them?
[2019%2009-00-32]
It makes it impossible to do any editing on a block instance in shaded mode!
Using the latest Nvidia Studio Driver on a 1080 and Rhino V6 SR20 (although it has been like this since I started using Rhino and I’ve seen it on multiple computers).
NOTE: This glitch goes away when you close the Block Edit.
And the only thread that I’ve ever seen getting any traction at all:
[image]
This is the worst UI part of Rhino.
I mean, why would you do this to a user, and then, in the BlockManager not show any layers?
[image]
I bet Block 3 - 9 are also on that layer, but I don’t know.
This and filleting is why Rhino currently is only suitable for small surfacing jobs.
The worry now, perhaps, is that the same 5 people are seen posting in all of these, and McNeel thinking that the rest of their customers have no issue with it… though nobody from McNeel has ever given me any satisfactory answers in any of my threads regarding blocks, so I don’t believe that is the case for a second.
6 Likes
