GetBoundarySegments method of spatial elements support added #187
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Awesome, thanks |
NeVeSpl
added a commit
to NeVeSpl/RevitDBExplorer
that referenced
this pull request
Nov 28, 2023
… of spatial elements support added
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the Pull Request
Adding support of displaying GetBoundarySegments method of SpatialElement class:
User can now see all the boundary segments depends on SpatialElementBoundaryOptions in 8 variants.
For boundary segments users can now see its IDs and length in Name in Left Panel to quickly analyze room boundaries.
Added 2 classes: SpatialElementDescriptor and BoundarySegmentsDescriptor
Quality Checklist