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. This has merit beyond supports, but as a principle could be applied to almost every command that uses an assignment list, such as section properties (shown with a reference in the GUI dialog) , specifications (which currently dont but would make sense to do something similar to be consistent), materials. The challenge with items like Section Properties is that the identifier Ref is a combination of both section profile AND material. Hence in the input file a line entry for a given section profile in the STD file which has been assigned to members 1 to 10, but members 1 to 5 have been assigned one material, say 275 steel and 6 to 10 assigned 355 steel. That means in the UI, there will be two entries in the table R1 and R2, but both refer to the same profile in the STD file. In short, the idea has merit and will be added to the backlog, but the implementation will need careful consideration and not as easy as you might have thought.