You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be very helpful to see what is returned without having to click on a method or property.
For example, the Element Members page lists methods such as ArePhasesModifiable with Public method icon and Description. Only after clicking on the method link can one see under Syntax that it returns a bool.
public[bool]ArePhasesModifiable()
Same with properties, such as AssemblyInstanceId. Under Syntax it shows that it is an ElementId.
public [ElementId] AssemblyInstanceId { get;}
Having that information available in the members page would save so many clicks:
Icon
Returns
Name
Description
bool
ArePhasesModifiable
Returns true if the properties CreatedPhaseId and DemolishedPhaseId can be modified for this Element.
...
ElementId
AssemblyInstanceId
The id of the assembly instance to which the element belongs.
...
The text was updated successfully, but these errors were encountered:
That would be great @onomou
revitapidocs mostly simply renders the documentation generated by autodesk revit developers (@jeremytammik)
so this change would need to be done by then.
It wouldn't be impossible to crawl documents to fetch types from deeper pages and then re-write the parent table, but that's not something I would consider since it could introduce errors and would require a lot of work.
I think it would be very helpful to see what is returned without having to click on a method or property.
For example, the Element Members page lists methods such as ArePhasesModifiable with Public method icon and Description. Only after clicking on the method link can one see under Syntax that it returns a
bool
.Same with properties, such as AssemblyInstanceId. Under Syntax it shows that it is an
ElementId
.Having that information available in the members page would save so many clicks:
The text was updated successfully, but these errors were encountered: