You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows 11 & OpenGL ES 3.0 & Renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
Issue description
Since 4.0 (or since this commit?), GDScript supports setting types for signal parameters, which is great, and I think setting types for parameters somehow makes the code easier to understand.
However, after reading some code about signal, I found that this type is not actually used, and the setting type is only supported because the parameter handling of signal is consistent with the normal function parameter handling.
This leads to the result shown in the picture below.
It can be seen that the type of the parameter shows a var, which is too puzzling.
Steps to reproduce
To attach a GDScript to any node, add a custom signal, such as:
signaltest_signal(arg1: int, arg2, arg3: float)
Click on the node to view the signal preview box of the node.
Minimal reproduction project
Not very necessary.
The text was updated successfully, but these errors were encountered:
Life4gal
changed the title
The node signal preview box does not show the type of the signal parameter.
[4.x] The node signal preview box does not show the type of the signal parameter.
Sep 15, 2022
In fact, until in e01b828, the parameters of custom signals do not support typed parameters. Maybe it could be written in that way, but the parameter type doesn't resolve to the specified type. You can emit other Variant values for the parameter specified as int.
extendsControlsignaltest(number : int)
func_ready() ->void:
test.connect(_test)
test.emit("test!")
func_test(arg):
print(arg) # Prints "test!" with no error.
Godot version
v4.0.alpha.custom_build [d9e974c]
System information
Windows 11 & OpenGL ES 3.0 & Renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
Issue description
Since 4.0 (or since this commit?),
GDScript
supports setting types for signal parameters, which is great, and I think setting types for parameters somehow makes the code easier to understand.However, after reading some code about
signal
, I found that this type is not actually used, and the setting type is only supported because the parameter handling ofsignal
is consistent with the normal function parameter handling.This leads to the result shown in the picture below.

It can be seen that the type of the parameter shows a
var
, which is too puzzling.Steps to reproduce
To attach a
GDScript
to any node, add a custom signal, such as:Click on the node to view the signal preview box of the node.
Minimal reproduction project
Not very necessary.
The text was updated successfully, but these errors were encountered: