-
Notifications
You must be signed in to change notification settings - Fork 3
Changing to using BHoM join instead of RhinoJoin when converting polycurves to avoid Rhino Crash #221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have not yet tested this Pull Request, only performed a code review.
My request for changes relate to the spelling on the comments and request for a date.
My other comments are for discussion, happy for them to be shot down as 'invalid' and resolved if appropriate.
Co-authored-by: Fraser Greenroyd <[email protected]>
@BHoMBot check compliance |
@FraserGreenroyd to confirm, the following checks are now queued:
There are 1 requests in the queue ahead of you. |
@BHoMBot check required |
@FraserGreenroyd to confirm, the following checks are now queued:
|
The check |
The check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks fine, test script looked ok (didn't dig into it too deep). Happy to merge this to alpha for further testing by alpha users before we go to the next beta.
@BHoMBot check ready-to-merge |
@FraserGreenroyd to confirm, the following checks are now queued:
|
FAO: @FraserGreenroyd The check they wish to have dispensation on is ready-to-merge. If you are providing dispensation on this occasion, please reply with:
|
@BHoMBot this is a DevOps instruction. I am authorising dispensation to be granted on check ref. 6129722289 |
@FraserGreenroyd I have now provided a passing check on reference |
NOTE: Depends on
Issues addressed by this PR
Closes #220
Using BHoM Join instead of Rhino join to check if the curve can be coverted.
This is to avoid full blown crashes of Rhino from happening that can for some cases be triggered by the Rhino.Join method that was used.
Test files
https://burohappold.sharepoint.com/:f:/r/sites/BHoM/02_Current/12_Scripts/02_Pull%20Request/BHoM/Rhinoceros_Toolkit/%23221-AvoidCallingRhinoJoinToStopRhinoCrashWhenConvertingPolycurves?csf=1&web=1&e=UMB25Z
Changelog
Additional comments