We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v4.1.1.stable.mono.official [bd6af8e]
Godot v4.1.1.stable.mono - Windows 10.0.22621 - Vulkan (Compatibility) - Intel(R) Iris(R) Xe Graphics (Intel Corporation; 30.0.101.3118) - 12th Gen Intel(R) Core(TM) i7-1255U (12 Threads)
Code generation for signals generates invalid C# code.
While the generated function stub is fine, it's placed at the very end of the .cs file, outside of the class definition.
Expected result: Method definition should be generated inside its respective class definition.
Follow the official "step by step" guide, the problem is visible in this step: https://docs.godotengine.org/en/stable/getting_started/step_by_step/signals.html#connecting-a-signal-in-the-editor
The text was updated successfully, but these errors were encountered:
Duplicate of #18721
Sorry, something went wrong.
No branches or pull requests
Godot version
v4.1.1.stable.mono.official [bd6af8e]
System information
Godot v4.1.1.stable.mono - Windows 10.0.22621 - Vulkan (Compatibility) - Intel(R) Iris(R) Xe Graphics (Intel Corporation; 30.0.101.3118) - 12th Gen Intel(R) Core(TM) i7-1255U (12 Threads)
Issue description
Code generation for signals generates invalid C# code.
While the generated function stub is fine, it's placed at the very end of the .cs file, outside of the class definition.
Steps to reproduce
Expected result:
Method definition should be generated inside its respective class definition.
Minimal reproduction project
Follow the official "step by step" guide, the problem is visible in this step:
https://docs.godotengine.org/en/stable/getting_started/step_by_step/signals.html#connecting-a-signal-in-the-editor
The text was updated successfully, but these errors were encountered: