EnhancedEglRenderer #261
Merged
EnhancedEglRenderer #261
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
venkat0907
changed the title
venkat0907
force-pushed
the
EnhanceEglRenderer
branch
from
25b0d6d
to
275f598
Compare
yashrajsapra
requested changes
Jul 17, 2023
yashrajsapra
approved these changes
Jul 17, 2023
venkat0907
force-pushed
the
EnhanceEglRenderer
branch
2 times, most recently
from
abe26e4
to
0cbecdd
Compare
venkat0907
force-pushed
the
EnhanceEglRenderer
branch
from
0cbecdd
to
b52ea64
Compare
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.
IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #243
Description
implemented two new features, one was creating & destroying EglRenderer window during run time , the other was adding flag through which renderer can or can't be manager via window manager
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
NO
Type Choose one: Feature
Screenshots (if applicable)
Checklist