You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just an idea for a new convenience feature. That is PROTOs that make those horribly nested scene trees manageable. When one need to make a PROTO from a node on a scene, the current workflow looks like this:
Create a new empty PROTO
Open the saved world in a text editor, find and select the text of the sub-tree to be converted
Copy this text to the new PROTO, managing not to mess up 'IS' fields vs literal fields,
Figure our parameter fields, JS scripts and such
Replace the original subtree with the new PROTO
Suppose you have a context menu command on a tree node, which takes this node and all its subtree, converts it into a new PROTO (with a wizard dialog similar to the existing one), then cleanly replaces the subtree with the new PROTO. You'd still have to figure out what goes into the parameter fields, write scripts and such, but the conversion itself would be so much easier!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
Just an idea for a new convenience feature. That is PROTOs that make those horribly nested scene trees manageable. When one need to make a PROTO from a node on a scene, the current workflow looks like this:
Suppose you have a context menu command on a tree node, which takes this node and all its subtree, converts it into a new PROTO (with a wizard dialog similar to the existing one), then cleanly replaces the subtree with the new PROTO. You'd still have to figure out what goes into the parameter fields, write scripts and such, but the conversion itself would be so much easier!
Beta Was this translation helpful? Give feedback.
All reactions