Fine grained saturation and contrast #185
Merged
Conversation
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
|
Super nice addition works amazing, should allow people to have more control, I also like having no limits could make for some cool screenshots and filters |
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.
This turns our saturation and contrast dropdowns into percentage number fields. I've left them with quite relaxed ranges, and included mentions of intended use in their tooltips instead of forcing some more sensible limits.
Requested by
PleaseRephrase&Clarify #8471on Discord and in this PR on the old repo: RS117/RLHD#138Please let me know if you think we should set some more sensible limits. Some examples of what you can do with these limits:
