Destroying nodes

#1

In mixed-mode Famous, removing nodes is tedious because all the sub-nodes need to be recursively removed by the app. After removing all of a node’s child nodes, the app has to also dismount the node and remove the node from the parent. It’s unnecessary boilerplate in the application IMHO and should be handled by the engine.

My proposal is for the engine to traverse all of a node’s children and recursively remove them whenever the app removes a node. This reduces chances of memory leaks and allows for much more elegant dynamic insertion & removal of nodes.

1 Like
#2

Whatever the ultimate solution, I agree that proper node removal should be a priority. It was a nightmare in Mixed Mode.

#3

The Mixed Mode API was intended to work the way you’ve described (in theory), but it didn’t because it was buggy. We’ll make sure ours works. ;}