8000 Use proper state lifecycle method for nulling renderer state changed handler by ycherniavskyi · Pull Request #216 · flutter-webrtc/flutter-webrtc · GitHub
[go: up one dir, main page]

Skip to content

Use proper state lifecycle method for nulling renderer state changed handler #216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

ycherniavskyi
Copy link
Member

Currently used deactivate method can be called many times during a state lifecycle.
(For example, it called several times during animation, which occurs when Scaffold with
RTCVideoView is shown with regular route push animation.)

Actually, subclasses should override deactivate method to clean up any links between
this object and other elements in the tree (e.g. if you have provided an ancestor with
a pointer to a descendant's RenderObject). / adapted quote from State objects lifecycle

…handler

Currently used `deactivate` method can be called many times during a state lifecycle.
(For example, it called several times during animation, which occurs when Scaffold with
RTCVideoView is shown with regular route push animation.)
Actually, subclasses should override `deactivate` method to clean up any links between
this object and other elements in the tree (e.g. if you have provided an ancestor with
a pointer to a descendant's RenderObject).
@cloudwebrtc
Copy link
Member

LGTM

@cloudwebrtc cloudwebrtc merged commit bc8dc67 into flutter-webrtc:master Apr 4, 2020
cloudwebrtc added a commit that referenced this pull request Jul 4, 2020
…nged-handler-nulling

Use proper state lifecycle method for nulling renderer state changed handler
@ycherniavskyi ycherniavskyi deleted the fix-odd-renderer-state-changed-handler-nulling branch December 11, 2020 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0