queue_free is acting funny.

v33to

		print("Before Removal")
		print($dice_pane.get_children())
		
		for d in $dice_pane.get_children():
			#if !dice_keep.has(d.name):
			print("Removing a Dice" + str(d.name))
			# Disconnect from signals
			#d.disconnect("remove_dice_from_keep", self, "remove_dice_from_keep")
			#d.disconnect("add_dice_to_keep", self, "add_dice_to_keep")
			# Remove the dice node
			d.queue_free()
			
		print("After Removal")
		print($dice_pane.get_children())

Output:

Before Removal
[[Control:1901], [Control:1911], [Control:1917], [Control:1923], [Control:1929]]
Removing a Dice :: dice
Removing a Dice :: @dice@2
Removing a Dice :: @dice@3
Removing a Dice :: @dice@4
Removing a Dice :: @dice@5
After Removal
[[Control:1901], [Control:1911], [Control:1917], [Control:1923], [Control:1929]]

What is even weirder is that the nodes physically leave my 2d scene. So I'm guessing what is happening is that in the time it takes to reach the bottom of my removal script, the nodes haven't been deleted yet. How can I correct this? I do some other operations at the end of the button press function that calculates a score and such and it's including the dice nodes that are supposed to be deleted.

TwistedTwigleg

queue_free puts the node on the queue to be deleted, it deletes then at the end of the next _process call, I believe. Off the bat, there are a couple ways you could work around the issue:

1: Use a yield: yield(get_tree(), "idle_frame") after calling all the queue_free calls but before doing any further calculation.

2: In the script that looks over all the nodes, you can check if the instance is valid, which should (I believe) be false if a node is queued for deletion:

# go through the nodes using whatever method I'll just assume
# each node is assigned to a variable called "node_here"
if (is_instance_valid(node_here) == true):
	# do whatever you need to do here!
else:
	# this node is queued to be deleted!
	pass

v33to

@TwistedTwigleg said: queue_free puts the node on the queue to be deleted, it deletes then at the end of the next _process call, I believe. Off the bat, there are a couple ways you could work around the issue:

1: Use a yield: yield(get_tree(), "idle_frame") after calling all the queue_free calls but before doing any further calculation.

2: In the script that looks over all the nodes, you can check if the instance is valid, which should (I believe) be false if a node is queued for deletion:
# go through the nodes using whatever method I'll just assume
# each node is assigned to a variable called "node_here"
if (is_instance_valid(node_here) == true):
	# do whatever you need to do here!
else:
	# this node is queued to be deleted!
	pass

Ahh yes. TY!

I posted the same question on godot reddit. Best suggestion I got from there was to use remove_child() then queue_free(). I'm still learning, so which do you think is a better solution?

TwistedTwigleg

Either would work, so I'd ultimately go with whatever works best for you. That said, if it was me, I'd go for checking to see if the instance is valid, as then you don't have the potential of nodes hanging around with parents.

v33to

GG TY.