Allow detail to be Loaded from Config #5
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
Load detail from the config node like the other recolor variables
Fix the value stored to detail being divided by 255 instead of 100
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 will allow detail to be loaded like the other recolor variables. Not sure why it was originally excluded from being loaded, but I found it cumbersome to have to adjust the value every time I loaded a preset. Current presets would need to be updated otherwise when loading a preset without a value saved for detail the value will default to 0 instead of the current default of 100. I submitted a pull already to LazyPainter so that it will save the value of detail for all new created presets.