(nevermind, I was stupid) Collections: Suggestion for auto naming at creation time
UPDATE: I have self rejected this, as I realized I don't need to suggest things to developers because I had been stupid. Copying the prior name is what blender already does. It isn't the software's fault if the user overwrote the entire auto-name, rather than just appending to it.....
I really like the new collections system, however I find the auto-naming scheme to be a bit lacking, Specifically as relates to advanced modelling work, where a library (or multiple) are used for sub assemblies.
Collection Hierarchies are very powerful, but when linking between libraries the hierarchies are flattened out and you are presented with a simple list. Trying to remember which set of parts is within which hierarchy is daunting, especially when you have already modeled hundreds of compound objects with similar components (e.g. which machine uses BOLTS.018? Crap, open second instance of Blender and look). Not saying that this has happened just now to me, but... hypothetically.
Suggestion is on the auto-naming upon creation of new sub collection: rather than inherit just parent name + .### (and since the names are in a shared namespace , it does not necessarily start with the next number), the new name could inherit the entire tree name, e.g. "TRUSS.StageFront.Upper.Section1.000" rather than just "Section.083" for example. The user would then be able to change the 000 to Bolts, for instance, and even if they don't they have some useful names that aren't just arbitrarily numbered around the scene.
Since collections are also the connection point for linking objects between scenes, this same naming convention will assist here. where if it was me I would make sure the source collection name was always without numbers (and indicated its source library /scene).
Now we have these proper named layers concept, a powerful addition to work organization, we can think about some polishing to really make them shine.
Of course, what I'm suggesting can be done manually, but it involves a lot of "double click, select some, dammit wrong selected, just retype the whole thing," typing text already known to the program.
1 Comment
I self-rejected this, as I realized the trouble was of my own cause, so no action needed here.