Expose main thread's looper for runOnUiThread compatibility #198
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
markkimsal
force-pushed
the
expose-main-looper
branch
from
677aeb7 to
53b965f
Compare
markkimsal
force-pushed
the
expose-main-looper
branch
from
53b965f to
edf5f87
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.
Posting to the UI thread is only possible via the looper obtained from the main activity thread.
android-activitycreates theAndroidAppinside a worker thread and there is no way to access the main thread's looper. Even interacting with the UI will send events into theAndroidAppInnerlooper and execute code in the worker thread.This PR simply records a pointer to the thread's looper before spawning the worker thread and makes it available in a similar fashion to the existing looper.
Related discussion:
#197