Make the names of faces, edges and tops of parts perennial for assembly

[leiopar]

Is there an existing issue for this?

• I have searched the existing issues

Problem description

Hi
let’s say I create a piece by extrusion, then that I use it in an assembly in the link via a face, a segment or a vertex.
If I refine the part with a simple chamfer, all the faces, segments, and vertex are renamed, which breaks the joints in the assembly.
For example, in a part: after an extrusion, I have a face called "Pad001.Face5".
I insert the part into an assembly using the face for a joint. The joint "reference1" parameter contains "Body002.Pad001.Face5".
But if I make a simple chamfer on a edge, even if it does not concern the "Pad001.Face5" side, this side is renamed to "Chamfer001.Face12" which is no longer recognized by the assembly.
Each task having a unique name, the name conflicts are impossible, so why not keep the original name ?
Note : even if the chamfer was made on an edge of "Pad001.Face5", nothing forces this face to change its name even if it is trimmed. Mathematically, it’s always the same plan.
thank you for your time

Full version info

OS: Windows 11 build 26100
Architecture: x86_64
Version: 1.0.2.39319 (Git) Conda
Build type: Release
Branch: (HEAD detached at 1.0.2)
Hash: 256fc7eff3379911ab5daf88e10182c509aa8052
Python 3.11.13, Qt 5.15.15, Coin 4.0.3, Vtk 9.3.0, OCC 7.8.1
Locale: French/France (fr_FR)
Stylesheet/Theme/QtStyle: FreeCAD Dark.qss/FreeCAD Dark/Fusion
Installed mods: 
  * A2plus 0.4.68

Subproject(s) affected?

PartDesign / Assembly

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[luzpaz]

Sounds like Toponaming.
Check out the improvements in the development build https://github.com/FreeCAD/FreeCAD/releases

[leiopar]

I had not seen this page in my research. But yes, it is indeed to this problem that I propose a simplified approach.
So, what do I do? I delete this issue and copy it into the wiki discussion ?
Sorry for the unexpected duplicate ...

[maxwxyz]

@drwho495 isnt this what you are working on?

[drwho495]

this is something that complex find would fix

[leiopar]

(thank you for conversion Issue ==> Discussion)
Note: I am indeed using a version 1.0.X. However, despite what is said in the wiki, the subject does not seem to be initiated there.

[drwho495]

@leiopar you might want to try this development build, it has a checking algorithm that typically fixes this issue

[drwho495]

Certainly. But why change this name with each operation? I can understand that this is necessary for certain other parts of FreeCAD, but why not create a "Name" parameter (which currently does not exist for faces) consisting of a unique identifier of the operation that created the face and a final face number?

I test a same face before and after chamfer with this code and I did not find a suitable parameter :

print("\n\n")

docname=FreeCAD.ActiveDocument.Name

print("docname", docname)



import FreeCADGui

Selection=FreeCADGui.Selection.getSelectionEx()

#print(dir(Selection))



for obj in Selection: 

	print("-------------------------------")

	print(obj.ObjectName)

	print(obj.SubElementNames)

	#print("dir(obj)",dir(obj))

	#pprint(obj)

	

	for subob in obj.SubObjects:

		print("-------")

		print(subob)

		print("getElementName",subob.getElementName)

		

		print("getElementIndexedName",subob.getElementIndexedName)

		print("hashCode",subob.hashCode())

		print("Tag",subob.Tag)

		

		#print(dir(subob))

You are looking for the ElementMap and ElementReverseMap. They have the (typically compressed/hashed) names.

The number after stuff like Face1, or Edge3 is just the index in a loop where that specific element is found. We cannot control the order in which those elements are placed.

[leiopar]

The number after stuff like Face1, or Edge3 is just the index in a loop where that specific element is found. We cannot control the order in which those elements are placed.

I understood well. The idea is not to control the name, but to not rename the same object (face, vertex, segment) 36 times. Once he has a name, leave him that name. I feel like I’m not clear, sorry.

[drwho495]

The number after stuff like Face1, or Edge3 is just the index in a loop where that specific element is found. We cannot control the order in which those elements are placed.

I understood well. The idea is not to control the name, but to not rename the same object (face, vertex, segment) 36 times. Once he has a name, leave him that name. I feel like I’m not clear, sorry.

That's because we do a Boolean operations on the previous shape of the model which causes stuff to be renamed.

[leiopar]

That's because we do a Boolean operations on the previous shape of the model which causes stuff to be renamed.

It is not a fatality, a boolean operation will not impact all the elements of an existing volume and nothing prevents them from returning their names to those who are simply truncated. Only the new faces, edges, and vertex require new names.

[drwho495]

That's because we do a Boolean operations on the previous shape of the model which causes stuff to be renamed.

It is not a fatality, a boolean operation will not impact all the elements of an existing volume and nothing prevents them from returning their names to those who are simply truncated. Only the new faces, edges, and vertex require new names.

We don't control that 🤷