Replies: 2 comments 1 reply
-
One difficulty is that multiple nodes may have different metadata keys available (and/or different values to them, but it's less of a concern here). Should we only display a metadata key when all selected nodes have the metadata key in question set, or should we display it as soon as one of the nodes have the metadata key set? In this case, what should changing the metadata do? Should it automatically create the metadata on the other nodes where it doesn't exist yet, or only set it if already existing? |
Beta Was this translation helpful? Give feedback.
-
To expand on the need for something like this with a real world use case, since I'm just now running into this myself. I use Cyclops Level Builder and more recently discovered a handy addon Material Footsteps which uses a metadata to determine what sounds to play. I agree, when multi-selecting nodes, only shared metadata tags and the option to add a new metadata should be present. Maybe a tooltip or something to note this? But that seems the most straight forward to me. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Metadata is really powerful, but when you select multiple nodes in the editor, the ability to add metadata disappears, meaning you can only add metadata to a single node at a time. This makes adding metadata to multiple nodes rather tedious.
The editor should support adding/editing metadata to nodes when multiple nodes are selected, similar to how editing any other property in the editor will edit the relevant property for each selected node.
Beta Was this translation helpful? Give feedback.
All reactions