New steps starting now:
3 new constraints as there are:
- point Identity
- point on line
- point on plane ()
This will have instantly effect to my rudimental topological naming, which only covers planes and edges and not vertexes. And this only with fc0.16.
Using vertexes within the muxInfo-entry of my importPart-Object will increase filesize to much. I shurely will have to change datastructure.
Nevertheless i will implement the constraints mentioned above now and will deactivate toponame checks for it.
(if topological naming is deactived, updating Parts to the assembly will possible break constraints, when parts have been modified)
So the question to the forum:
Is there anything like following pseudocode available for python:
Code: Select all
constantFaceNames = {}
for i, face in enumerate(Part.Shape.Faces):
constantFaceNames[i] = Part.getFaceTopoName(i) # <=== this is the important point
Same i would need for Vertexes, Edges.
The resulting names should be robust to most common modifications of a part.
I think topological naming for purpose of assembly does need to be so perfect as for PartDesign. Almost at beginning.
Machinery designers ( i am one ) mostly fix parts together by fitting planes, axes, drilling holes, some important vertexes and so on.
Fixing parts together by constraining small fillets, chamfers and other complicated things can be necessary, but not so often.
So what i want to say:
Does anyone here have such thing or is working on it ? Is something in the pipe ? Really ready or not even. Accessible for python!
Or do i have to rework my own toponamer (it is a hell)
Each help is appreciated.
kbwbe