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
We need API for Scope Boxes to be able to control visibility and size.
The workflow today is way to manual. With the API for Scope Boxes we could make tools that would make the control of sizes and visibility way more easy to handle.
It would be very interesting feature to allow user to change geometry of scopebox via API. Allow to change the geometry obtained from get_Geometry(Options) method? Ideally user should be allowed to set the X,Y extents of the scope box by selection. Allow to snap the edges of selected scope boxes to selected family in GUI as well as via APIs.
It would be great if the Scope Box class is made more accessible through the API. Currently, it seems like there is no way to modify existing scope boxes easily if at all via the Revit API. For example, It is not possible to access/modify existing Scope Box parameters such as Views Visible directly from the API. I attempted to do this by collecting all Scope Boxes in the document using the BuiltInCategory VOLUME_OF_INTEREST and then tried to extract the parameter value of the BuiltInParameter VOLUME_OF_INTEREST_VIEWS_VISIBLE. However, it seems to be non-UserModifiable and it kept returning nothing. I tried snooping the Scope Box parameters using Revit LookUp and it seems like this parameter is not user modifiable.
The more I mess around with Dynamo, the more I keep running into this brick wall with Scope boxes. If you could set the location of scope boxes through the API, there are so many possibilities for parametricizing workflows and packing loads of function into a project template file. Scope boxes are almost the smartest feature in Revit, and it's wild to me that they stop just short of being incredible
Scope boxes aren't fully exposed in the API. They don’t even have their own class; they belong to the Element class. They also don’t have parameters like width and length. So, please create a subclass like ScopeBox and a constructor that takes a BoundingBoxXYZ object as it's argument. That would be great.
Scope boxes have been a long-standing limitation in the Revit API. After all these years and despite numerous votes, they still don’t have a dedicated class, they’re just generic Element instances with minimal accessible data. I can’t even get basic properties like width and length, which severely restricts any meaningful automation or manipulation. Can we please get a proper ScopeBox class exposed in the API?
