I certainly will try it out later this evening (studying for my certification right now) but is there any more detailed/advanced explanation about why I can't run a bunch of code in a thread and at the end of the thread start a dialog? Why I have to start a nested thread with just the dialog creation? :s Still don't really get the reason why...
Anyway thx in advance for giving me a possible working solution, and I'll certainly keep you informed if it did the job for me (later this evening). On 21 jan, 19:47, TreKing <[email protected]> wrote: > On Thu, Jan 21, 2010 at 12:28 PM, Dirk Vranckaert > <[email protected]>wrote: > > > So if I understand you correct I should run two nested threads to show > > the dialog? > > Yup. So instead of showDialog(int) in the thread, do > runOnUiThread(someThread); where someThread just calls showDialog(int) in > it's run method. > > Yes, it's annoying and messy, but you can't do UI related operations in > separate threads, so there you go. > > ------------------------------------------------------------------------------------------------- > TreKing - Chicago transit tracking app for Android-powered > deviceshttp://sites.google.com/site/rezmobileapps/treking
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
