Async and Message Naming Rubric #1160
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Make setState (which sends an UpdatEngine to the serialization thread) wait for the unstream to complete to correctly meet the plugin api requirement of synchronous set state. Closes surge-synthesizer#1157 2. Add a rubric for how message names should be set, and start a few, but not many. Addresses surge-synthesizer#1141. Did a partial merge since I had started but the new name had only been applied to set engine state and didn't want conflict pain in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Make setState (which sends an UpdatEngine to the serialization thread) wait for the unstream to complete to correctly meet the plugin api requirement of synchronous set state. Closes Plugin state load is async #1157
Add a rubric for how message names should be set, and start a few, but not many. Addresses message names and message objects are a mess #1141. Did a partial merge since I had started but the new name had only been applied to set engine state and didn't want conflict pain in the future.