Possible questionable use of signals

Xrayleader

Hello, this isn't an issue as of now, but i would like a second opinion:

I have a timer signal that i'm using to change levels, which i'm sort of reusing, the method of reusing it is disconnecting it, changing it's variables and connecting it again, it has worked so far, the only side effects are errors detected on the console, they spell "ERROR: Disconnecting nonexistent signal 'timeout', slot 1234: levelchanger" or "nonexistent signal 'timeout', slot 1234: levelchanger". Again, i'm not having issues so far, but i would like to prevent them while i can. If someone has a better method of changing levels after a timer ends or a better method to reuse timers i'm all ears as well.

Xrayleader

My apologies, i just realized i didn't put my code, here it is:

transitionover.disconnect("timeout", singleton, "levelloader")   
transitionover.connect("timeout", singleton, "levelloader", [value1,value2])

TwistedTwigleg

I think that should work. I generally just use a simple timer in code in _process for level changing, rather than a timer, but the gist is the same regardless.

As for the issues, it seems both issues are caused by trying to disconnect a signal that is not there. You may want to add the following condition before calling disconnect (discovered thanks to this Reddit post):

if transitionover.is_connected("timeout", singleton, "levelloader"):
	transitionover.disconnect("timeout", singleton, "levelloader"
transitionover.connect("timeout", singleton, "levelloader", [value1, value2])

Xrayleader

That's actually the solution i came across, and for the record to anyone who comes across the same issue, it works :]

Thank you very much for your input :]