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
Describe the bug In the Signals documentation at https://docs.dialogic.pro/classes/class_dialogicgamehandler.html?highlight=signals#signals, there is a timeline_ended signal defined. While this signal does appear to be present in Dialogic, it does not fire nor run code.
To Reproduce Steps to reproduce the behavior:
func test(): print("this should print"
Expected behavior Func test or func anything I define should run when the timeline ends. It does not.
Screenshots
System (please complete the following information):
Possible fixes
The signal needs to be reworked so that it fires correctly, I'm not sure there's a second way to go about it.
The text was updated successfully, but these errors were encountered:
Not sure what exact version of alpha 17 Wip you are using, but this seems to be working fine on the current main branch for me.
Sorry, something went wrong.
No branches or pull requests
The problem
Describe the bug
In the Signals documentation at https://docs.dialogic.pro/classes/class_dialogicgamehandler.html?highlight=signals#signals, there is a timeline_ended signal defined. While this signal does appear to be present in Dialogic, it does not fire nor run code.
To Reproduce
Steps to reproduce the behavior:
func test(): print("this should print"
Expected behavior
Func test or func anything I define should run when the timeline ends. It does not.
Screenshots
System (please complete the following information):
Solution
Possible fixes
The signal needs to be reworked so that it fires correctly, I'm not sure there's a second way to go about it.
The text was updated successfully, but these errors were encountered: