Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I love how Autodesk likes to let things sit, untouched and unacknowledged, for about 5 years before they deign to "put it on their roadmap." And that's if we're lucky. I get that they need to offer new tools to stay ahead of their competition, I really do, but if you're neglecting provably broken "features" in favor of these new ones, your software development team's heuristics are all sorts of wack. I mean, the complete lack of end-user centricity in their releases is appalling, disguising is as a simple "lack of community interest" until it's such a festering issue they think it'll look good and people will be thankful that they finally fixed it. Every feature added becomes the foundation of how your software is perceived in future updates, and continuing to build on that broken foundation while your clients (yes, we as the users of their software are their target consumer/client base) are very vocally complaining about the very obvious cracks that don't get fixed update after update is going to ultimately doom the software because of people's lack of faith. If not now, then in the future, because today's users are tomorrow's project managers and other higher ups that make the decisions for which software to use.
This is still an issue in Revit 2022. If you select the tag of a reference drafting view, Edit Type, and change the Reference Label (SIM, OPP, etc.) it changes all tags of the referenced view because it is a parameter of the view instead of an instance parameter of the label.
Has anyone found an acceptable workaround to this (other than dumb text next to the tag)?
Still a problem Autodesk, definitely fix this, it's a decade overdue.
But while you're at it, just make view tags be able to have user generated instance parameters so a view bug can have unique properties when it shows up in different views, such as varying the size or masking region by drawing. And speaking of masking regions in view bugs....
it is stuff like this that makes me think issues like this get ignored on purpose. more clicks and more time spent by our users means that we need more users. more users = more licenses for Autodesk. Solving problems and adding features like this actually hurts Autodesk's bottom line.
Prove me wrong Autodesk. Fix small things like this that will improve the experience for your users.
Congrats! We think this is a great idea, so we've decided to add it to our roadmap. Thanks for the suggestion!
To follow the progress of features in development, please see the Revit Public Roadmap and join the Revit Preview Release to participate in feature testing. (Note that Accepted Ideas may not be immediately available.)
