-
Notifications
You must be signed in to change notification settings - Fork 14
Remove in Grasshopper
Note: Before reading this page, it is recommended to have a look at Using the BHoM section.
Having the adapter successfully set up, one can start interacting with Revit. In general, Remove
action is very similar to Pull
(although instead of pulling it deletes elements). Remove
component behaves like a standard Grasshopper component, so can be placed on canvas with a standard double left click action. Request, on the other hand, is a solely BHoM type, therefore it is easiest to invoke it with Ctrl+Shift+B menu, with an alternative of using CreateObject
component (CreateRequest
is currently on prototype stage and does not capture all Requests).
The example below shows a simple exercise of deleting all Revit sheets using category filter. There is a few details that might be worth noticing:
-
FilterByCategory
allows to switch off case sensitivity. This is a general use for most name matching components in Revit_Toolkit. - Remove will not run as long as it is not activated (
active == true
).
More examples is available in Remove examples page.
-
Overview:
What is Revit_Toolkit for?
Code structure
Building from source and debugging
License
Sample scripts -
Adapter:
Basics
Revit <-> BHoM conversion
BHoM vs Revit identity
Handling of Parameters
Conventions
Setup in Revit
Setup in Grasshopper
Setup in Dynamo
Setup in Excel
Details -
Pull:
Basics
Requests and filtering
Pull of Geometry and Representation
Pull from Links
Pull in Grasshopper
Pull in Dynamo
Pull in Excel
Examples
Explicit family vs type mapping
Details -
Push:
Basics
Push modes
Updating Revit types
FamilyLibrary
Push in Grasshopper
Push in Dynamo
Push in Excel
Examples
Details -
Remove:
Basics
Remove in Grasshopper
Remove in Dynamo
Remove in Excel
Examples
Details -
References:
BHoM Wiki
BHoM Adapter