Yes, that's what I'm looking for. In that connect
code you posted, you're basically telling that script to listen for the connected2
signal, and when it's received to call a function named Area2D
- also found in the current script.
That 2nd error you posted is saying that the script does not have a function named Area2D
- which I assume is correct.
That 1st error indicates that a 2nd script is also listening for the connected2
signal, and when it's received, it's trying to call a function called onArea2D2connected2
- which also doesn't exist.
In the original code you posted, it seems like you're expecting to call _on_Area2D2_connected2
when the signal is received, but that's not what you defined in the connect
code.
Again, according to the errors, it's looking for a script named Area2D
from one place and a script named onArea2D2connected2
in another.
Though, I think the underscores in those function names are causing some rendering trouble here in the forum. Posting the errors inside code tags would fix that...
Bottom line, find your connect("connected2", ...
statements (there are at least 2) and see what the 3rd argument to the is. That's the method that will be called when the signal is received. If that method doesn't exist (as in your case), you get the errors you reported.