should this be considered as a bug for android application. Usally, when people use keyboard, they are sending some information to server. After that UI will be updated in call back.
On Jan 23, 10:20 am, "James Patillo" <[email protected]> wrote: > Yeah, threads are particularly fun to deal with in Android. > > -----Original Message----- > From: Stanley.lei [mailto:[email protected]] > Sent: Friday, January 23, 2009 11:52 AM > To: Android Developers > Subject: [android-developers] Re: Activity Issue on G1 phone > > I rather agree with you! > > In fact, I could not understand why Google designs like this. The > keyboard action could impact the rotation, but why changing rotation > impacts the activity? In my case, the thread is destroyed, which will > destroy all tasks in the thread. In worst case, the user will have to > re-create their data from scratch. > > stanley > > On Jan 24, 1:47 am, cindy <[email protected]> wrote: > > Then android's implementation has problem. > > > For example, if my application needs to create account, of cause, the > > key board will open first. After user typed in user name and password, > > then he clickes the "create" button.Request sends to server in a > > thread. After that, he closes the keyboard, the activity will be > > destroyed. So the callback function in thread to update UI will > > crashed. > > > It happens exactly in my application. > > > On Jan 23, 7:20 am, "James Patillo" <[email protected]> wrote: > > > > I think what happens is that the activity's state is saved, the activity > is > > > destroyed, and then it is recreated with its saved state. This is the > same > > > thing that happens when the home button is pressed and the app is > reopened. > > > > This just what I have come to understand, and may be wrong. > > > > -----Original Message----- > > > From: Stanley.lei [mailto:[email protected]] > > > Sent: Friday, January 23, 2009 9:04 AM > > > To: Android Developers > > > > Cc: [email protected] > > > Subject: [android-developers] Activity Issue on G1 phone > > > > Hi all, > > > > I met a very strange issue when I tested my application on G1 phone. > > > > As usual method, I started a thread in an activity, and stopped the > > > thread in the onDestroy method. But to my surprise, when I tried to > > > slide down the keypad, the onDestroy method was called and the thread > > > was stopped, and more surprising thing was that the activity was still > > > alive and visible. > > > > From the activity's life cycle > diagram,http://code.google.com/android/reference/android/app/Activity.html, > we > > > can see that onDestroy is called only before the activity is shut > > > down. But my activity is still active and visible!!! > > > > Who could tell me what the hidden story is? > > > > Any reply will be appreciated. > > > > Thanks, > > > > Stanley --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
