Closed feiss closed 5 years ago
I wonder if we'd think about this differently if we framed this tool as complementary to code rather than a end-to-end tool. If so, then we could prescribe developers group their entities if they want to do a batch transform. This is a good prescription because if we are trying to do the same transform operations to multiple entities, then they probably belong in a group in code.
<!-- Grouping in code. -->
<a-entity position="5 0 0">
<a-box></a-box>
<a-box></a-box>
<a-box></a-box>
</a-entity>
vs:
<-- Output of multi-select and applying individually. -->
<a-box position="5 0 0"></a-box>
<a-box position="5 0 0"></a-box>
<a-box position="5 0 0"></a-box>
FWIW, with Chrome's Developer Tools, you can pretty sloppily copy and paste anything from the Styles inspector and the resulting clipboard output is correct. Can we do something similar?
best practice to group entities?
Multiple selection and grouping are different things, you may want to modify multiple entities (ie. Moving the same distance) that are completely unrelated among them..
But it's ok, I didn't miss this feature much.
"It's ok" as in "yeah ok, we can live without this --although any serious app have this feature" :oD
Multiple selection is a complex issue, but it could be simplified and limited to basic operations like transforms and simple edits:
S= list of current selected objects
If more than one object is selected: