Removes a child from the container by tag value. Virtual void removeChild (Node *child, bool cleanup = true) To remove a child from the parent node: // Removes a child from the container. Virtual void addChild (Node *child, int localZOrder, const std::string &name) Virtual void addChild (Node *child, int localZOrder, int tag) Adds a child to the container with z order and tag. Virtual void addChild (Node *child, int localZOrder) Adds a child to the container with a local z-order. To add a child to the parent node: // Adds a child to the container with z-order as 0. Delete them all in one go, iterate on the list of children, etc… You can assign a name or tag to them for easier access. You can get a pointer to them to access them. There are all sort of methods related to parenting. Lets have a look at the different methods we can use here: Methods to call from a Parent Node
The lower the z order is the more priority they have for drawing on the screen. The z order will define which of the children will be drawn before the other ones. The tag and name will help us refer to the children nodes easier. This is not all! There are other options that you can set when parenting to a node. Inside the init() method of our HelloWorld.cpp we had: this->addChild(myNode) Until now, we had to use the simple parenting method addChild() that attached our nodes to the main scene that runs in the app. This is useful when you have a game character or vehicle and you want to parent independent moving parts to it, like weapons or turret, etc… Unlike in real life, where children usually don’t listen to their parents! This allows us to change the transformation of a parent node and cause its children nodes to follow suit and do the same.
One of the features of the Node class is that you can parent them together and create a hierarchy of nodes.
0 kommentar(er)
