Make Prev/Next Segment UID classes standalone #124
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
robUx4
added
api-break
They are not KaxSegmentUID as they don't have the same ID. If we need a special class for Segment UIDs (including chapter ones) we should use a proper class/interface. Eventually this should be moved into KaxSemantic like KaxSegmentUID.
robUx4
force-pushed
the
prev_next_uid
branch
from
0619cc6
to
06a772e
Compare
mbunkus
approved these changes
Dec 19, 2023
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.
They are not KaxSegmentUID as they don't have the same ID. If we need a special class for Segment UIDs (including chapter ones) we should use a proper class/interface.
Eventually this should be moved into KaxSemantic like KaxSegmentUID.