WIP: Android activity lifecycle management#1293
Closed
blaind wants to merge 4 commits intobevyengine:mainfrom
Closed
WIP: Android activity lifecycle management#1293blaind wants to merge 4 commits intobevyengine:mainfrom
blaind wants to merge 4 commits intobevyengine:mainfrom
Conversation
Member
|
I'm not an expert on android app development, so I can't comment directly on the "proper way to handle android lifecycle events in winit" side of things without doing more research. But I really appreciate that you're digging in to this. Thanks! |
Contributor
Author
|
This has progressed in other issues (referenced in #86, I'll close) |
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
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.
This is a proof-of-concept implementation of Android activity lifecycles into
bevy_winitcrate.For background, see:
Various comments:
So far, this handles the following cases:
Also,
SaveInstanceStateand the accompanying resume state (?) need to be handled.Various logs of lifecycle events
Log of lifecycle events reported by android (added println! statement in winit crate)Log printed with various debug items in bevy crate as well: