Make Tags Smarter

[Anonymous]

Tags need a little help. For example

1. We need to be able to stretch a keynote tag, or a multi-category tag so that we can wrap the text. Having to create multiple Types for small, medium, and large is too much work. Give us the ability to add multiple leaders to these tags

2. We should be able to add Parameters to some tags, like Section Tags, and have them show up when loaded. I have found that some tags will not carry this data forward when loaded into a project.

3. Key Schedule Shared Parameters to happen so that we can add this info to tags. Would greatly help with Occupancy Calculations.

4. I am sure I am missing a lot more here. Feel free to add to this list.

Sash Kazeminejad

Ideate, Inc

[steezzen]

I agree with all of this, particularly number 3. It is maddening that there is no way to have a tag that automatically calculates an area's occupant load.

[Anonymous]

One thing that I would like to add to my original post. It would be nice if we could specify leader attachment points inside of a tag and keynote family. For example, Room Tag leaders are annoying depending on the position of the tag relative to the leader. Sometimes the leader start point ends up in some really weird places.

WE REALLY NEED BETTER TAGS. THIS IS FUNDAMENTAL FOR ANY PROGRAM. 

[kadenk3AKS5]

1000% agree. Came onto the forum to finally get around to posting this, and it is good to see others have already had the idea. Only downside is it appears to still only be gathering support after 8 years. The capability to have instance parameters in tags would be incredible. There are so many great use cases besides the obviously benefit of no longer having to have "Size 1, Size 2, Size 3, Size 4....." tag types in order to avoid the dreaded Multi-Line tags that can't be driven by formulas if we simply had the drag nodes like available in text.

In addition, it would be incredible to have instance visibility parameters to create popup text like "Optional" in front of the main text, or "Flush" vs "Dropped" Beams, or "SEE DETAIL", or Show Border. Obviously you can do that all with creating tons of Types (Tag Example-Size 1-Optional-Border, Tag Example-Size 2-Optional-Border, Tag Example-Size 3-Optional-Border, Tag Example-Size 1-Optional, Tag Example-Size 2-Optional, Tag Example-Size 3-Optional, etc) but the list grows exponentially fast as soon as you want to add any sort of creative style or tiny bit more technical detail that does not need to be a part of the model element to a tag. 

Instance Based Tags would reduce the Types to "Tag". Which is MUCH more manageable.

For the time being, I have put formulas into the tags to read "Optional" if Optional is Check on the model, etc, but you still end up have tons of types because labels with no information leave an invisible "box" when printed (generally somewhat solved by a " " instead of "". You still have an invisible box that messes up your leader location now, so it makes more sense to have yet another tag type). So many workarounds to achieve smart, flexible tagging without having unmanageable amounts of tag types.

Also, the ability for adding ANY sort of additional parameters to keynote tags would be amazing. The keynoting concept is totally there, but it is too restricted (which I know it is meant to be) but it needs some quick additional text every now and then without having to go create an entirely new keynote for a one-off element.

Thanks for your consideration!