Closed huskier closed 8 months ago
I miss the point of this and find it confusing. Selection is done in the original coordinate system of the parts.
@adam-urbanczyk Hi, Adam, This issue is related to #1538. It is originated from the understanding of the following constraint.
# top
.constrain("top@faces@<Z", "con_tl?X", "Plane")
Through making a pre-arranged initial parts layout, I think the constraints become more straightforward.
# top
.constrain("top@faces@<X", "con_tl@faces@>X", "Plane")
That is exactly the same constraint. What is exactly more readable here? Also, you are not using tags, which is one of the things that the example is trying to demonstrate.
I seriously don't understand what was your question in #1538. It reads as if you did not get how assy constraints work, even though it is quite exactly specified in the docs.
OK, Let's forget this issue and the issue of #1538.
It is quite complicated to understand the constraints of the enclosure door assembly example code in the assembly tutorial section. I've tried an approach to improve the readability of the example code.
To assemble the parts, I've firstly made them, and then put them in relative rough positions. In this layout state, I've set the constraints. In this way, it is much better to understand the constraints, at least for me. Actually, it's the GUI's manner (such as Solidworks, UG, and Creo etc.) to assemble models.
Here is my source code. I could do a PR if people think it is useful.
If I've done a rotation or a translation to a part, the tagged mating assistants are not useful since the coordination system has changed.
At present, I do not know how to improve the handle part code.