Thanks Frank, its a very good idea. I'll have to rewrite the interface code to accommodate it. I'm currently using an alert dialog to present the user with the button to click or cancel. It executes the Asynctask, and calls a second alert dialog with a new button to press or cancel. Right now the second alert dialog appears as soon as the first button is pressed. That is the reason why I wanted to wait for Asynctask to return.
I guess I could try calling a new alert dialog in the onPostExecute(), but I don't think I can do that? On Jul 6, 11:57 am, Frank Weiss <[email protected]> wrote: > The second button should be disabled while the first asynctask runs. > When it finishes, the second button is enabled. > > You don't need "global variables". You can save the results in > instance fields of the activity. -- 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
