Skip to content
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

Family Instance on MEPCurve connectors fix #1269

Merged
merged 1 commit into from
Oct 11, 2022

Conversation

michal-pekacki
Copy link
Contributor

NOTE: Depends on

Issues addressed by this PR

Closes #1267

Placing family instance on MEPCurve doesn't work for specific cases (sloped pipes). This fix changes connector location check from IsAlmostEqual to DistanceTo to avoid null connector values.

Test files

Changelog

Additional comments

@michal-pekacki michal-pekacki added the type:bug Error or unexpected behaviour label Oct 3, 2022
@michal-pekacki michal-pekacki self-assigned this Oct 3, 2022
@michal-pekacki
Copy link
Contributor Author

@BHoMBot check required

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 5, 2022

@michal-pekacki to confirm, the following actions are now queued:

  • check code-compliance
  • check documentation-compliance
  • check project-compliance
  • check core
  • check null-handling
  • check serialisation
  • check versioning
  • check installer

There are 8 requests in the queue ahead of you.

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 5, 2022

@michal-pekacki just to let you know, I have provided a check-versioning result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @michal-pekacki on BHoM

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 5, 2022

@michal-pekacki just to let you know, I have provided a check-installer result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @michal-pekacki on BHoM

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 5, 2022

The check versioning has already been run previously and recorded as a successful check. This check has not been run again at this time.

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 5, 2022

The check installer has already been run previously and recorded as a successful check. This check has not been run again at this time.

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 6, 2022

@michal-pekacki just to let you know, I have provided a check-versioning result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @michal-pekacki on BHoM

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 6, 2022

@michal-pekacki just to let you know, I have provided a check-installer result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @michal-pekacki on BHoM

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 7, 2022

@michal-pekacki just to let you know, I have provided a check-versioning result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @michal-pekacki on BHoM

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 7, 2022

@michal-pekacki just to let you know, I have provided a check-installer result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @michal-pekacki on BHoM

@michal-pekacki
Copy link
Contributor Author

@BHoMBot check copyright-compliance
@BHoMBot check dataset-compliance

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 7, 2022

@michal-pekacki to confirm, the following actions are now queued:

  • check copyright-compliance
  • check dataset-compliance

There are 34 requests in the queue ahead of you.

@michal-pekacki
Copy link
Contributor Author

@BHoMBot check ready-to-merge

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 11, 2022

@michal-pekacki to confirm, the following actions are now queued:

  • check ready-to-merge

There are 10 requests in the queue ahead of you.

Copy link

@travispotterBH travispotterBH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested in Revit 2018 on several different slope values on different sized pipes. Works well. Happy to approve.

@travispotterBH
Copy link

@BHoMBot check ready-to-merge

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 11, 2022

@travispotterBH to confirm, the following actions are now queued:

  • check ready-to-merge

There are 10 requests in the queue ahead of you.

@michal-pekacki
Copy link
Contributor Author

@BHoMBot check ready-to-merge

@bhombot-ci
Copy link

bhombot-ci bot commented Oct 11, 2022

@michal-pekacki to confirm, the following actions are now queued:

  • check ready-to-merge

@pawelbaran pawelbaran merged commit b9a44dd into main Oct 11, 2022
@pawelbaran pawelbaran deleted the Revit_Tools-#604-FireCollarPlacement branch October 11, 2022 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Error or unexpected behaviour
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Family Instance on MEPCurve connectors fix
3 participants