Hey! I have this file where there are a few blocks that I can’t select or delete, and a number of layers I can’t select or delete. Apparently there are no objects on the layers, but c’mon, I can see them on the screen! But I can’t select them, I am driving nuts here. It’s like a phantom. What i can do is to turn off the layers that contain the objects…
All the basics have been tested, such as:
no hiding objects, no layers locked or turned off, etc.
Any tips to get rid of all this? Am I missing something really obvious? In that case you can of course laugh after letting me know…
Hi Monica- if there are blocks in the file and the objects in the blocks are on those layers, you will not be allowed to delete the layers. If there are blocks in the file but no instances of them anyplace, use Purge to remove the block definitions and then your layers should be available to delete. You can also BlockEdit an instance and move the parts from the block onto other layers. Feel free to post the file or send to email@example.com.
I run bad objects and they’re not there.
I tried already block edit, but… as I said, I can’t select them.
I already purged, but the block definitions won’t go because they’re actually there: I can see them.
This is the funniest thing: I just typed Explodeblock>selectall, and they all exploded. I select all the lines and deleted… and the blocks stay underneath. Exploding just created a copy of it. Weird!
I am sorry, but it’s a design flaw to marry a block definition to any layer–because it doesn’t have to be on any.
After dealing with this, I now create ALL of my definitions on the “default” layer. From there, I put the instances on which layer I want. It’s a poor compromise, but it’s better than searching for definitions.
[This is one of the only 3 things I dislike about Rhino, the others being the texture replacements didn’t work in blocks, and the block manager is quite paltry for counting objects.]