Open
Conversation
dennisss
force-pushed
the
ocs-breakpoints
branch
2 times, most recently
from
e06ac2e to
30a9da3
Compare
dennisss
force-pushed
the
ocs-breakpoints
branch
from
30a9da3 to
c69e753
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
📖 Summary
OCS currently returns a cue when firing
startmessages. Previously gcs did nothing with this, and just played upon receiving the firststart. To support starting from an arbitrary breakpoint, a check for cue number has been added.🔍 Details
Needs testing.
✔️ Testing
✔️ Verification