Tags (that are outside the Block Definition) can’t reference VA Elements placed inside Rhino Blocks.
This limitation effectively disables this workflow unfortunately.
1 Like
Hi @Czaja, how do you expect this to work? I mean, if you have a block with more than one VisualARQ object, and you create a tag for the block, which object inside the block should the tag be linked to? why don’t you create the tag inside the block, instead?
I would expect a list of VA Objects that are taggable and that I can choose one.
Having tag in a Block is a mess. For example if I would do it this way and have, 4 block instances, then every block instance will be always tagged which is something undesired.
@Czaja do you mean you wish to have two identical block instances (of the same block definition), and tag them differently?
That sounds a bit unusual, since block instances are meant to be identical, aren’t they?
I’m not sure if this is feasible, (for example, you cannot use text fields of objects inside a block in Rhino, if you are not in Block Edit mode), but we will study it.
Well, no. It’s something completely normal. There could be zillions of its usability. Even with VA objects one can have the same “block” (let’s say a column) with different sizes. Aren’t they still the same block?
Some eons ago Autodesk introduced blocks with attributes. It was one of the best features of AutoCAD (another one was a clipped external block). I frankly cannot understand why there is such a strong resistance at McNeel / Asuni about this 
Cheers, Jaro
I’m interested to see (just) a couple of examples of it.
Sure
The first one: wooden beams, one of them with a firesafety coating. I would use one single definition, with additional tags. The second: concrete columns, one of them prefabricated, the rest monolithic. Also, as one single definition. The third: when working on a conceptual design I would not distinguish many other objects. I think I would use a single door for all doors, a single window for all windows. But I may need to get different descriptions of these “blocks”.
All these object would “look” the same, with different non-geometrical quantties. And so on.
Thankfully, there could be parameters, and these quite fit me. But these parameters, aren’t they just advanced tags?
Cheers, Jaro
1 Like
@jerry.bakowski thanks. We will study if this feature is feasible in future versions.
I simply mean that I won’t add a tag to a block, because then every instance of the block will always have that tag, and maybe I only want to tag one and leave the rest untagged.
I was also hoping to use Blocks that have a single VA Element and some Rhino geometry in them. Such an element behaves differently than a regular VA Element when it comes to tagging, and the important thing is that it behaves similarly/the same. There are too many inconsistencies, workarounds needed already.