Use ColorManagement better when constructing Colors #16
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
Solid-three will never set a color without using ColorManagement.workingColorSpace, or a color space passed to us explicitly. Mainly, we want to avoid Color setters that default to SRGB, so the user has better control.
After discussion, we concluded that the declarative style should use the Three.js defaults, even if we doubt their approach. Users of `solid-three` can always set colors imperatively if they want to have precise control.
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.
Solid-three will never set a color without using
ColorManagement.workingColorSpace, or a color space passed to us explicitly. Mainly, we want to avoid Color setters that default to SRGB, so the user has better control.