STAAD.Pro Ideas Portal
Welcome to the STAAD.Pro Ideas portal. The purpose of this site is to post ideas for enhancements and new features. We value your feedback and our team regularly reviews your suggestions for consideration in future releases.
You have 3 options for providing feedback:
Vote for an existing Idea. The popularity of an Idea helps us understand its importance to our users.
Comment on an existing Idea. We want to hear your unique point of view.
Add a new Idea. If no existing Idea describes what you would like, add a new one!
When you Vote, Comment, or Add an idea you will also be subscribed to that Idea and will receive status updates. Please note that we may merge or rename Ideas for clarity. Thank you for your support and feedback, it is always appreciated!
Thank you for posting this idea. Reactions can be annotated in 2 ways, 1) in a box as a standard annotation with a leader to the relevant node or as an arrow scaled by its magnitude in the selected directions. It is the former method I believe you are referring to.
As I am sure you appreciate, there is a fundamental difference between the way the model and annotations are rendered. That is a model exists in 3D space called 'model space' which is why it can be rotated. However, annotations are rendered on in a separate environment over the top of the 3D model called 'paper space'. This means that it is a challenge to retain relationships between the 3D model and annotations as views are opened/closed and resized.
Saying that, I believe that there is an opportunity that could be investigated to allow for your idea. That is by providing an Annotation Management tool in which every annotation that is created is given an id and retained with the auxiliary data (where views and the like are hosted). This tool could then be used to activate/disable each defined annotation.in any view. The location of the selected annotation would then be displayed in the paper space associated with the given view relative to the top left corner of the active view.
Also if annotations could be driven by OpenSTAAD, then an automation/macro could be used to generate standard annotations.
Would that solve your problem?
This is still sorely needed. I'm constantly having to re-select my annotation choice. I know it only has one vote, but I really don't think many people review these ideas.