Hi, jordy1989,
Yes, I have a lot of single objects, that I wish could get a list/export of, without resorting to turning them into blocks. I thought that any user named object could be put in a list. In other words, important enough to give a meaningful name.
(Sometimes, I just don’t want to lock up objects by blocking them, as it’s more difficult to change their materials, their layer, or their properties.)
[To the block manager’s credit, I can do a multiple select and get a list of multiple blocks in the pop-up, but that usefulness was not intuitively indicated.]
In the mock-up, the metaphor was a flat list, the kind you would want if you were buying parts–such as 609 fasteners! The problem with the hybrid flat/hierarchical list is, I cannot tell which objects are root objects, and which ones are made from others. The list only shows me one compartmentalized branch/twig of the tree of a project, and not an expanded tree, nor a list of all objects. You have to craw/drill-down the list exhaustively to learn what you have and need.
Until Rhino has both a full flat view and a tree view, I will not nest blocks, because it’s just not worth the trouble, and I will always create them on the default layer, and move them after they are made. If someone has told me to these things, it would have saved me a lot of work. In another thread, I cannot get anyone to care or understand that I don’t want a block definition to be linked to any layer, only the instances, which I want to move from layer to layer with abandon : )
Take Care,
Brenda