Getting Child Nodes - organiation question

This might be my inexperience talking, but doesn’t it make way more sense to have the Node’s responsible for having their own small dictionaries, and then returning their own children, rather than having to query the Selected Dialogue and to have it return the children of whatever node we pass in? It just seems rather round-about and it feels like Dialogue “knows” too much about the nodes in that way.

The Dialogue needs to know the relationships between the nodes and their children to draw them properly in the Editor. Keeping these things in the nodes would make issues like deleting nodes much more difficult. Since the Dialogue is already tracking the nodes and their relationship for this purpose, it makes sense to keep the organizational structure.

1 Like

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.

Privacy & Terms