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 would like to have access to at least read the Revit Link Display Settings through the API. I want to be able to see if a filter in the Link file is being applied and if the current view is using the link display settings or the main file's settings.
Yes Please allow access to control the Links override settings.
Just like we can override categories for the current model itself also allow us access to the linked models category override settings, just like in the UI.
Maybe use a override of current methods, like call it with RevitLinkType ElementId or a RevitLinkInstance ElementId to edit only one instance (just like in the UI)
Inside Revit Templates, inside the V/G Overrides Revit Links, there is an option for setting the Display Settings for each Link as Custom. I would like to manipulate these Custom settings using the Revit API.
For a file with maybe 100 view templates, each template has to be hand edited on--by-on at the outset of each project to turn off consultants levels, grids and annotation. There is no way to build this settings into our view templates.
Please implement this feature, or add a filterfunction, which can hide categories from all RevitLinkInstances in the specific view. This would not be perfect, but better than nothing 🙂
@kimberly.fuhrman these are related VIA View templates, the latter are linked view templates but exposed in the API should (hopefully) be the same class/wrapper:
@kimberly.fuhrman these are related VIA View templates, the latter are linked view templates but exposed in the API should (hopefully) be the same class/wrapper:
@kimberly.fuhrman these are related VIA View templates, the latter are linked view templates but exposed in the API should (hopefully) be the same class/wrapper:
