New Feature: Listenable Say Dialogs #1064
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As requested by someone on the Fungus Community Discord, I made a system that makes it so that through code, you can listen for when a Say Dialog starts and stops executing a Say Command. It was originally released here (please check the User Guide): https://drive.google.com/drive/folders/1FTRuqGiqi8xx_qF02O8tCD50S0ThABWn?usp=share_link
This PR has the code copied over from that, but with the appropriate changes applied. Stuff like making sure it's under Fungus's namespace, the SayDialog component is edited directly instead of subclassed, etc.
What is the current behavior?
There's nothing that lets users respond to when Say Dialogs start or end without having to change their copy of the Fungus source directly.
What is the new behavior?
Through a new class, SayDialogSignals, user code can listen for... well, you know at this point.
Important Notes