I've always used Activity.RunOnUIThread to do my UI threading, and MvvmCross goes to a lot of effort to track the current Activity so that it can always marshall code back to the UI thread if it needs to.
However... having read lots of the Android documentation, it feels like the UI thread in an Android application is just the UI thread, and that's it the same thread that's used for all activities throughout a single application.
Is this the case?
If it is, then do I have to use Activity.RunOnUIThread? Or can I just capture the thread identity somehow (perhaps using SynchronisationContext.Current) and then run things on that thread regardless of what the current Activity is?
Stuart (wondering if this question made any sense)