[android-developers] Re: Proper way of handling orientation change + async thread

2008-11-03 Thread Greg
When you change orientation your Activity is destroyed and then re- created. When you re-create the dialog view object that was sent to the background process is no longer valid, thus the error. There are probably several ways to handle this but the first that comes to my mind is: 1) The backgr

[android-developers] Re: Proper way of handling orientation change + async thread

2008-11-04 Thread zl25drexel
Thanks for your reply, any example codes? On Nov 3, 8:28 pm, Greg <[EMAIL PROTECTED]> wrote: > When you change orientation your Activity is destroyed and then re- > created.  When you re-create the dialog view object that was sent to > the background process is no longer valid, thus the error. >

[android-developers] Re: Proper way of handling orientation change + async thread

2008-11-05 Thread zl25drexel
well i am answering my own question again. I figured out a working solution, for those who are interested, see http://bend-ing.blogspot.com/2008/11/properly-handle-progress-dialog-in.html On Nov 4, 9:52 am, zl25drexel <[EMAIL PROTECTED]> wrote: > Thanks for your reply, any example codes? > > On

[android-developers] Re: Proper way of handling orientation change + async thread

2008-11-05 Thread Fish Kungfu
Maybe we need a "Self Help" section. ;-) Thanks for posting your self-answers, since they still help everyone. On Wed, Nov 5, 2008 at 1:08 PM, zl25drexel <[EMAIL PROTECTED]> wrote: > > well i am answering my own question again. I figured out a working > solution, for those who are interested, se

[android-developers] Re: Proper way of handling orientation change + async thread

2008-11-06 Thread Kyle
Does anyone have anymore examples of handling this? I've been trying everything including zl25drexel's workaround and I've had no luck. I tried dismissing the dialog in my onDestory() method and then used onRestoreState() to redisplay the dialog but it still never gets dismissed. Any help would be