Cannot access child property after add_child func

leakzz

I cannot access to my node property (Label for my case.) right after it was added as a child of my container. Im trying to get its prosition in the container (VboxContainer) but if I try to get position after add_child() it's always (0,0) but if I get_position in _process() or trying to get the previous child added it has the correct property ... like if it wasnt updated fast enough after add_child and have to wait until the next add_child inside that container.

Here is an example of my concern:

var label = Label.new()
    label.text = "Label"
    var label2 = Label.new()
    label2.text = "Label2"
    vbox.add_child(label)
    vbox.add_child(label2)
    print("Position: ", label2.rect_position) --> output(0,0) NOT OK HERE

but in _process :

func _process(delta):
    if Input.is_action_pressed("ui_accept"): # do not worry just for avoiding spamming on my console ^^
        var label2= vbox.get_child(vbox.get_child_count() - 1)
        printt("label2:", label2.rect_position) ---> output ("0,14") OK HERE
```

TwistedTwigleg

I would guess that the reason the labels are not positioned correctly is for two reasons.

The first reason is they do not have their position set when they are created, so you are getting the default position. Godot defaults to a position of (0, 0), so if you want to position the nodes, you'll have to change them after calling add_child (You may be able to move the nodes before add_child, but it has not worked for me)

The reason the positions are updated in _process is because the VBoxContainter node has had time to reposition the labels. The container has to update before it can move its children into position, which means another _process function call (or whatever the container uses to reposition nodes) has to go by so it can reposition its children.

Because you have just created the label and are checking it's position, you are going to get (0, 0) because the container has not had a chance to update and reposition the nodes yet, but the container will in the next _process call, which is why you are getting the correct values in _process.