lp1912965: Mark newly created cues as dirty#3599
Merged
Merged
Conversation
...otherwise they won't be saved. Fixes https://bugs.launchpad.net/mixxx/+bug/1912965
Closed
Contributor
Author
|
|
daschuer
approved these changes
Jan 25, 2021
Member
daschuer
left a comment
daschuer
left a comment
There was a problem hiding this comment.
Oh, It looks like this was my dog food.
Thank you for the fix. LGTM
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
2 participants
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.
...otherwise they won't be saved.
Obviously caused by a refactoring. Since recently new cues are initialized when created instead of populating them incrementally which would then set the dirty flag.
Fixes https://bugs.launchpad.net/mixxx/+bug/1912965
Supercedes #3544