hi @WALIDGIO
This is a request you should make to the Autodesk team.
As explained, the suggestions presented here are intended to illustrate the capabilities of the Robot API. They are not necessarily tailored to your specific architecture and are shared as general-purpose usage examples, rather than definitive solutions for a particular or personalized implementation.
Regarding the use of the RobotBar class and the addition of direct-read properties from RobotStorey, I have a different point of view than changing the paradigm. The code provided consists of just a few lines and is based on selections made from text strings, which are very quick to process compared to some collections. overloading the bar class with properties that are only occasionally read is not ideal.
Instead, you can optimize access times in your code by better data management, changing your programming language, creating your own classes and parralelizing your queries. This approach would preserve the API's efficiency while allowing for the customization you need.
Best Regards
Stéphane Kapetanovic
Did you find this post helpful? If it gave you one or more solutions,
don't forget to accept the solution and leave a < like !
