We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Compound.do_children_intersect seems to have a side effect.
Compound.do_children_intersect
I use build123d/docs/tutorial_joints.py and add two debug statements:
build123d/docs/tutorial_joints.py
diff --git a/docs/tutorial_joints.py b/docs/tutorial_joints.py index e6d2fd3..b45e0f0 100644 --- a/docs/tutorial_joints.py +++ b/docs/tutorial_joints.py @@ -331,9 +331,11 @@ m6_screw.parent = box_assembly print(box_assembly.show_topology()) # [Check that the components in the assembly don't intersect] +print("DEBUG(1)", box.joints["hinge_attachment"].parent.volume) child_intersect, children, volume = box_assembly.do_children_intersect( include_parent=False ) +print("DEBUG(2)", box.joints["hinge_attachment"].parent.volume) print(f"do children intersect: {child_intersect}") if child_intersect: print(f"{children} by {volume:0.3f} mm^3")
It leads to the output
DEBUG(1) 1940751.7699835314 DEBUG(2) 0 do children intersect: False ``´
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Compound.do_children_intersect
seems to have a side effect.I use
build123d/docs/tutorial_joints.py
and add two debug statements:It leads to the output
The text was updated successfully, but these errors were encountered: