Add public Framebuffer.depth and Framebuffer.stencil properties
#9338
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
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
|
Hey @dev7355608 ! This is certainly a technically correct PR, but i can't think of a use case where this would be useful :D |
|
Yeah, probably unlikely that these properties are changed, but I thought why not: it can't really hurt to have it. |
bigtimebuddy
added
the
🥶 Low Priority
|
Nice |
1 similar comment
|
Nice |
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.
Description of change
I thought it might be useful if these properties are publicly accessible and can be changed with the framebuffer automatically updating.
Pre-Merge Checklist
npm run lint)npm run test)