Reevaluating Worldspace and Localspace Treatment (need some dev triage)

[Debuk]

I was hoping that a dev would recognize it and respond to this first. But then lets start directly collecting what could be done. Here are my thoughts on it.

@ivan_stephan: Could you please rename this thread to something like “Reevaluating Worldspace and Localspace Treatment (needs triage by developer) " or " Dont’t click this thread!!!” ;). Mainly please change it to something that raises some attention by the devs and makes sense for what this is about.

I’d propose renaming and redesigning things here and add new essential features.
I thinkt this will be the fastest way to get it done, but maybe even rethinking the tree structure would make sense.

First things first: The User doesn’t need to know anything about that parent inverse matrix. This (without inverse) is uncommon, misleading, generally it isn’t understood well and should be eliminated.

1. What we need is:

• Convert to Worldspace
• Convert to Localspace
• Treat Values As Worldspace
• Treat Values as Localspace

or do the same thing and call it alternatively

• To Worldspace (Convert Values)
• To Localspace (Convert Values)
• To Worldpsace (Keep Values)
• To Localspace (Keep Values)

2. The “convert values” options are the only ones that make sense as default. So every parenting option in the outliner, the sidebar etc should work that way.
   And a preference for if a user prefers localspace or worldspace additions would be welcome.

3. We also need a

• “Group Objects in Empty” (Parenting to Empty)
• “Dissolve Empty” (Remove an Empty and place the childs at the hierarchical level of the deleted empty, also with “Keep Values” or Convert Values" options)
• “Delete Object without Children” ( Same thing for Objects as Dissolve Empty )
• These should be avaiable in especially in the outliner context menu.

4. Things like the “To Localspace” command should work on multiple objects and should work in the 3dview as well as the outliner and perhaps also in the transform panel, via context menus and shortcuts

5. We need an Icon or a desciptor, or a even a toggle, in the transform section to make clear if this is localspace or wordspace.

6. The Outliner needs some visual differentiation for this too. May it be little icon additions like the counter for mesh objects on folded entries, or different colors for the whole main icon

• 

Things like this would be suffficient and that without the need of touching the internal treestructure at all.

I listed some of the drawbacks of the current implementation further above :

Reevaluating Worldspace and Localspace Treatment (need some dev triage)

How are object hierarchies typically handled? The object hierarchy in a 3d modeler or game engine normally consists of treelike structured “stacks” of matrices. As every object in a such a scene tree has such a matrix and everyone is interpreted to be relative to its parent, each matrix is operating in its parents space. We can multiply the matrices to get the final transform for calculating final positions for vertices of a child. Eg setting a child to position to 0,0,0 aligns its origin posit…

@julianeisel: I am not sure if you are the right one to ask, but you seem to be involved in the ui programming. Could you have a look at this? Lot’s of people miss these features and that way it shouldn’t be that much work. What do you think?