Remove automatic opacity migration for v3 opacity inversion#588
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
![kdevbot[bot]](https://avatars.githubusercontent.com/in/772429?s=60&v=4){kind=small}
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Remove automatic migration as part of #379
Release Notes
This removes the automatic opacity migration from v2 to v3 (2024).
Users using v3 or higher
No action is needed; your opacity settings have already been converted as part of the v2 to v3 update.
Users using v2
Update to v3 to have your opacity settings migrated, then to v5. As a reminder, the Use Inverted Opacity setting can still be used to preserve the inverted opacity (v2) behavior.