Signal method gets called within the editor and returns "not found" error

[mthreis]

By adding a signal method to a C# script (such as Control's _resized()), Godot calls it on the editor and returns the error:

core\object.cpp:1127 - Error calling method from signal 'resized': Control(Window.cs)::OnWindowResized': Method not found.

Script:

public class Window : Control
{
    void OnWindowResized()
    {
        var size = OS.GetWindowSize();
        OS.SetWindowSize(new Vector2(Mathf.floor(size.x / 2) * 2, Mathf.floor(size.y / 2) * 2));
    }
}

[akien-mga]

CC @neikeq

[akien-mga]

Can this still be reproduced in the current master branch?

[paulloz]

Yes, but this is not specific to C#. The same error occur with connections GDScript.

[aschuhardt]

Is there a known workaround for using signals with Mono?

[akien-mga]

Here's a minimal reproduction project from #19826: Example Project.zip

[Skaruts]

I have this issue but it's not related to C#, but to the tree_entered signal (and it's on a different line in the source code). I give a node that signal and connect it, and then when I switch scenes (when I switch back to this one) the editor throws that error in the output:

core/object.cpp:1261 - Error calling method from signal 'tree_entered': 'Control::_on_Control_tree_entered': Method not found.

Seems to happen with any kind of node, and both if the signal is connected to the node or the parent. (I also tried it in a blank project, and it behaved the same way.)

I tested this just now using a 3.1 nightly build from Hugo Lucurcio's site that I just downloaded.

I haven't tested other signals.

[neikeq]

@reduz Not a mono issue.

[Piet-G]

This would have to be solved in a way that it still allows for tool scripts to connect to those signals in the editor.

[akien-mga]

This would have to be solved in a way that it still allows for tool scripts to connect to those signals in the editor.

This is not specific to tool scripts, but to any node with a signal attached that can be called by the editor, when the editor itself uses this node (e.g. AnimationPlayer's animation_finished). See #13070 (comment)

[Piet-G]

@akien-mga Yeah I know. I just mentioned that because the first instinct might be just not to connect those signals while in the editor, but then tool scripts who might want to receive signals while in the editor would not receive them. That's why I mentioned them there.

If a signal like animation_finished was connected to a function in a tool script it wouldn't even produce an error since it would just call the function like normal.

[Poobslag]

I'm still encountering this error in Godot v3.2.2. If a setter/getter emits a signal, and is invoked in a tool script which connects to non-tool scripts, the console will log 'Method not found' errors.

tool
extends LineEdit

# Setting this 'melodic' value in the editor causes console errors.
export (String) var melodic: String setget set_melodic

signal melodic_changed

func set_melodic(new_melodic: String) -> void:
	emit_signal("melodic_changed")

Here's a simple reproduction project: signal-errors.zip

Editing the LineEdit's 'melodic' property in the editor throws errors as it tries to send a signal to a non-tool node. I'd expect the signals to just be tossed into the void.

[akien-mga]

Please open a new issue, this was fixed two years ago.