[update] order of destroy and init events #22
Merged
Conversation
This file contains hidden or 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
Update changes the order of events. Now, when view A replaces view B, events will go like next - B.destroy() - A.init() To do so, we remove direct destructor() calls from the rendering callback and place the same call just after rendering new UI ( after this point we don't need old view anymore )
Member
Author
|
Related sample added |
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.
Update changes the order of events.
Now, when view A replaces view B, events will go like next
To do so, we remove direct destructor() calls from the rendering callback
and place the same call just after rendering new UI
( after this point we don't need old view anymore )