View Issue Details

IDProjectCategoryView StatusLast Update
0000597FreeCADFeaturepublic2017-08-29 23:58
Reportergafvert Assigned To 
PrioritynormalSeverityminorReproducibilityN/A
Status newResolutionopen 
Product Version0.12 
Summary0000597: New feature naming convention
DescriptionI suggest a new more informative naming convention for new generated features (such as fillets, cuts, fusions etc). Right now the newly generated feature is only given the feature name and a number (if it's not the first).

You can see the history, of what it is based on in the project tree by expanding the item, but not in the name alone. So you usually end up with a lot of "Fillet012" and "Chamfer003" in the list.

My suggestion is to introduce a new first part in the naming convention, the name of the base object. Giving the standard format ObjectName_FeatureName_Number
This is to make it easier to keep track of your parts and which on is which without manually renaming them.

An example:
1. You create a box, and it is named "Box1".

2. You create a fillet on one of the edges of this box, it will be named "Box1_Fillet1". Using the name of the base object.

3. You create another fillet on this "Box1_Fillet1", this time, to make sure the names don't grow too much, the entire name isn't used for the base object name, only the ObjectName part. So the new fillet will be named "Box1_Fillet2".

4. This "Box1_Fillet2" is then cut using a boolean operation, and given the name "Box1_Cut1".

etc etc.

The same can then be used for all types of features, with new features being given names containing the based object name with the addition of a feature name.
TagsNo tags attached.
FreeCAD Information

Relationships

has duplicate 0002191 closedkkremitzki PartDesign Let features inherit the names of the sketches they are generated from 
related to 0001333 closedwmayer FreeCAD Extruding a shape "MyShape" should call solid "Extruded from MyShape" 

Activities

wmayer

2014-01-02 14:30

administrator   ~0004003

It's best to have an option in the preferences to add the base name or not.

Issue History

Date Modified Username Field Change
2012-02-08 12:50 gafvert New Issue
2014-01-02 11:27 wmayer Relationship added related to 0001333
2014-01-02 14:30 wmayer Note Added: 0004003
2017-01-19 12:55 Kunda1 Relationship added related to 0002191
2017-08-29 23:58 kkremitzki Relationship replaced has duplicate 0002191