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
starting a event from API with a cue name always starts the first matching event. Could it maybe start the next matching event
Should we also look into pattern matching on the cue names? example: start SFX.* would start the next sfx cue even if it was named SFX.1 or SFX.2
start SFX.*
The text was updated successfully, but these errors were encountered:
I am not sure about the second part. I personally never programmed a sequence where I would trust such wildcards.
But as for running the next matching cue, sounds like a good improvement to me
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
starting a event from API with a cue name always starts the first matching event.
Could it maybe start the next matching event
Should we also look into pattern matching on the cue names?
example:
start SFX.*
would start the next sfx cue even if it was named SFX.1 or SFX.2The text was updated successfully, but these errors were encountered: