-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
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
Godot tours 101 does not advance after clicking play button #4
Comments
Thank you for the quick response. Is there a reason for that? I’m new to godot, but not new to C#. Trying to get a lay of the land. |
I don´t know the exact reason at the moment. In the .NET version, somehow, we can't reliably poll the editor for some state changes, which is the approach we've chosen for this framework. We could instead use signals and that should work for the .NET editor, but given that:
I've decided to not support the .NET edition myself. If someone looked into it and could made sure everything works smoothly and reliably across Godot editions, I'd gladly take the contribution. I just can't spend the time myself now, as we have many deadlines lined up until August 30, 2024. |
@NathanLovato I believe this still works with the .NET version of Godot on 4.2.1 with some modification. See this issue: gdquest-demos/godot-tours-101-the-godot-editor#4 |
I'm submitting a...
Bug report
What is the current behavior?
Clicking the play button in the Godot Tours 101 app does not cause the checkbox to fill so there is no way to advance to the second step.
What is the expected behavior?
Clicking the play button in the Godot Tours 101 fills the checkbox so the second slide can be advanced to.
Tell us the steps to reproduce the bug, and if possible share a minimal demo of the problem.
Feature request
Describe the problem you're trying to solve.
Tell us which solutions you've explored, the solution you would pick, and why you think it would be the best for everyone.
Other
Other information
Godot.-.Recording.2023-12-28.103321.mp4
The text was updated successfully, but these errors were encountered: