2.8 Proposal - The Bane Of Renaming: Object + Object Data Names
Issue/Problem: Inconvenient Naming
- I actually want to know the reason(s) as to why there are separate naming fields for 'Object' & 'Object Data' . Please do inform me because I am probably ignorant as to why Blender does this. There has to be a reasonable meaning behind this decision that I clearly do not know.
- Now the problem. Gotta keep objects organized and naming things is a basic standard. But my goodness, the fact you have to rename both fields to keep things organised will become very tedious.
Solution/Improvement: Steel Locks
- If the two naming fields have critical reasons to exist, then throw a chain toggle in somewhere. Done, please.
This idea was marked as a duplicate of Option to Rename Mesh Data When Renaming Mesh Object.
6 Comments
Why? Multiple object can have single mesh data (you edit one, and rest is changed).
But yea, if there is single user of that mesh changing object could change also mesh name.
You can rename mesh data after objects using addons.
Having object names and data names in synch should be easyier. I agree. I wrote a renaming addon that includes also the functionality the rename the data blocks based on the object names. github.com/Weisl/simple_renaming_panel . You can rename the data for all objects or just the selected one. It takes the object name and a user specified suffix.
Or have a system in the Outliner that shows what is linked and what isn't the original parent of the mesh data. To show what instance is where.
@ondraise15: This used to exist in the 2.4x days. It was the "OOPS" view for the Outliner... a nice tree diagram that showed instancing relationships. It was always supposed to come back, but still hasn't. :(
@Jason van Gumster: Schematic view or nodal view needs to come back.
I remember that in blender 2.4x there was an auto button to do that, or something similar