On Mon, Apr 19, 2010 at 10:04 AM, tripy <[email protected]> wrote: > I know there is a lot of code, but I thought too much is better than too > few. >
It's a tough call, too much and people's eyes glaze over, too little and no one has any context to help. The link to the formatted code is a good alternative. If I find the time I'll look it over. > 1) Effectively, I discarded the getApplicationContext pretty fast. > Good. > 2) I know that the AsycTask is aimed for that exactly. > I just would like to understand why this code don't work now. I don't see > why a threaded object would not be good enough in that case. > Yeah, not sure, have't looked at it closely enough. > But I'm seriously thinking about rewriting my worker to an AsyncTask > That would be a good idea. > 3) Here, you lost me.... I was thinking that I was calling them from the > activity!? > I mean use Activity.showDialog(int) and Activity.dismissDialog(int) instead of calling dialog.show() and dialog.dismiss(). ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- You received this message because you are subscribed to the Google Groups "Android Beginners" group. NEW! Try asking and tagging your question on Stack Overflow at http://stackoverflow.com/questions/tagged/android To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en
