Conversation
Effects refactoring: fix segfault
Effects refactoring minor changes
…nd make use of it.
Fix empty effect chain selector after renaming chain presets
Contributor
|
Time is up. |
Member
Author
|
Thank you @Be-ing for merging this 11500 lines branch and taking back the responsibility to fix the pending issue and polish it for a release. Do you have a plan and schedule? |
Member
|
@Be-ing Please document new controls in the manual load_effect |
Contributor
|
We need to alias the old ControlObjects to coherent names before writing coherent documentation. |
This was referenced Aug 23, 2022
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
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.
This #2618 with its 957 comments, no longer usable in a reasonable way in the GitHunb GUI.
This branch is in a pre-mature state, but to make progress we have agreed to the following workaround proposed by @JoergAtGithub here: #2618 (comment)
During the last days I have verified all my original review comments and fixed minor issues myself. Some work is already included here and some PRs are still pendig:
#4466, #4461, #4487,#4482,#4483,#4484, #4486These PRs can be merged before merging this here or I will retarget them to main after merge.
Than I have created a number of Bugs
According to 2) of our commitment we need now one or more developers who are accepting the tasks to examine and fix the open issues that we are able to finally release this branch in a stable Mixxx 2.4. and update the manual accordingly.
Once we have such commitment, one of them may then merge it to main.
Thank you very much in advance.