It would be useful in many cases to be able to select text tags from more than one entity for a single label. For example here I show two labels, one showing the component’s description and the other, the face’s area.
Both work but they’re kind of clumsy.
FWIW, this was requested back in 2019, too.
The name of the “Entity” column is a bit confusing as it splits out “Face” which is an attribute. I think all the relevant attributes for a Group (or Component) including in addition to Volume, the placement coordinates, and bounding box dimensions (Len X,Y,Z), Total Surface Area, Area of associated/clicked face, Material of associated/clicked face & Tag should be available. Perhaps retain the entity names column but remove “Face” and have the “Choose Label Text” show ALL potential property labels for the associated entity.
Having the same basic attributes available for Groups as Components, without having to resort to Component creation would definitely be a bonus.
The ability to select the Parent & Grand Parent entity names would be handy as well e.g. it might supply the storey or assembly name or any other grouping name from Outliner.
Adding multiple names / attributes can be a pain, having the ability to preselect multiple names & attributes would be a powerful option. These can then be edited / sorted in place if necessary.
Edit: Added Tag to the wished for attributes.
I think Face as an entity makes sense. The entity list is determined by the structure in the model. Here I have the leader anchored to a face in a component inside another component.
I guess it depends on your perspective. The left column I see as being the equivalent of Outliner, the right column should be listing all the attributes of the entity at the leader anchor point. I thought this is the point you were making in your OP that you can’t list multiple attributes for a single entity?
In your latest post you can see the “Volume” attribute, but it could have just as easily included the face area and coordinates for labelling. I don’t understand the need to split the attributes in this way?
The request makes total sense, especially if we could retrieve as many attributes as possible with single leader and if we could organize them nicely and in an orderly fashion.
It would also be great if we could retrieve attributes from a viewport into Layout spreadsheets without needing a leader line, but by pointing at objects.
This spreadsheet should then be exported and updated when the model updates.
