![]() Another immediate consequence that comes to mind would be the question of what scripts containing (‘name’) should do. Opening a v4 file with v5 would require that a name group be converted to a hierarchical group which is not a function that exists now. Using v4 to open the 3dm file associated with the screenshots above has both objects named "sphere" get combined into a name group, so killing name grouping in v5 seems like it would be tolerated by v4. I'm sure that deprecating grouping by name would have consequences that I don't understand. Newly created objects that have not yet been renamed by the user could even get descriptive default names based on the operation that created them such as "Plane", "Loft", or "Name of Script". Or, newly created objects could just be thrown into the top level of the group hierarchy as is done in Illustrator and Corel. If a junk drawer is necessary, a group called something like "Unnamed" might be better. Unnamed acts like a junk drawer that's not only disorganized, but locked. Many operations don't do that, so then I have to run a script to select the last created objects, or I have to visually find the object that I wish to rename in one of the viewports, select it, and then go over to the properties panel to rename it. I can only easily assign it a name if the operation that created the object left the object selected. Now, every object that I make goes into the name group called Unnamed unless I take the trouble to give it a unique name. However, if I Ungroup the 2nd "foo" the 2 objects named "sphere" get combined into a name group, which might not be what I intended:Īn additional benefit of doing away with grouping objects by name involves "Unnamed". ![]() I can even give 2 objects the same name, but not have them be grouped if they are at different levels in the group hierarchy: I understand that this has been part of MoI for a long time, but now that you’ve come out with hierarchical groups, what is the value of name grouping? In addition to the disappearing object problem that new users like me may stumble over, it creates an inconsistency when coexisting with groups: I can give 2 groups the same name, but that doesn’t cause them to combine. ![]() One solution I see is to deprecate object naming as a means of grouping. I don’t expect coming to like this because of the vanishing object problem described above. What I don’t think I’ll like is clicking on an object name to assign that name to another, selected, object. In Illustrator and Corel I often have problems dragging an item through a long list in the Layers Palette so that I can drop it on another item for the purpose of grouping. I think I’ll come to like clicking on a group name to add a selected item to that group. But, now I know what’s going on in MoI v5 and simply hit undo. Since I switch back and forth between MoI, Illustrator, and Corel multiple times a day, breaking my habit of clicking object names to rename them will be difficult. I also make this mistake in v4, but there it’s benign because clicking an object name doesn’t do anything. Why did I click the name of an object in the browser? Because that’s how I edit object names in Illustrator and Corel: double click the name to make it editable. I now understand that the first object, being selected, was simply assigned the name of the second object, but it took some experimenting to figure that out. My immediate panicked reaction was that I had triggered some bug that caused part of my model to be deleted. Poof: a second object vanished from the browser. I was working on a model consisting of multiple objects and clicked on the name of a first object in the Objects section of the scene browser. I’ll describe my experience with naming and groups in v5, especially what happened before I had any understanding of groups.
0 Comments
Leave a Reply. |