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
Describe the bug
I don't know if this is a bug or normal behavior but when I provide a toolbox to drop in a component with multiple Elements nested, these do not show up as parent/child in the node tree data. This means in my custom layers I see only the top node. Upon inspection I find that top node has linked node, and those nodes are created properly, but they are not connected as children. Strangely though, in the UI they do appear nested, so maybe that relationship is maintained somewhere? Is this normal behavior? Because this is clearly a tree, I want them made as a tree rather than using linked nodes, which I thought would be the normal default behavior?
I realized after creating more nested Elements that the children further nested are stored in data.nodes[]. It's just this component itself where it is parented to ROOT or whatever parent it's dropped into, and it uses data.linkedNodes instead of data.nodes[] to store the reference to it's first child.
Describe the bug
I don't know if this is a bug or normal behavior but when I provide a toolbox to drop in a component with multiple Elements nested, these do not show up as parent/child in the node tree data. This means in my custom layers I see only the top node. Upon inspection I find that top node has linked node, and those nodes are created properly, but they are not connected as children. Strangely though, in the UI they do appear nested, so maybe that relationship is maintained somewhere? Is this normal behavior? Because this is clearly a tree, I want them made as a tree rather than using linked nodes, which I thought would be the normal default behavior?
The text was updated successfully, but these errors were encountered: