Dialog Survival Over Configuration Change

by Marco Nelissen » Thu, 05 Mar 2009 01:22:00 GMT


Sponsored Links
 


Why do you say that? Opening or closing the keyboard counts as a
configuration change, so it's something that can happen at any time.


Unless you take measures to avoid it, a configuration change will
cause your activity to be destroyed and recreated with the new
configuration. It goes through the normal activity lifecycle when
doing this, so to the current activity is paused, stopped and
destroyed, and the new activity is created, started and resumed.

--~--~---------~--~----~------------~-------~--~----~



Dialog Survival Over Configuration Change

by Romain Guy » Thu, 05 Mar 2009 02:57:05 GMT


 orry I got confused, you want removeDialog(), not dismissDialog().
The latter only closes the dialog but it is still known as a managed
dialog. removeDialog() on the other hand tells the Activity to forget
about the dialog *and* to dismiss it.

On Wed, Mar 4, 2009 at 10:53 AM, Nmix <nepean...@gmail.com> wrote:



--
Romain Guy
Android framework engineer
romain...@android.com

Note: please don't send private questions to me, as I don't have time
to provide private support. All such questions should be posted on
public forums, where I and others can see and answer them

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Dialog Survival Over Configuration Change

by Dianne Hackborn » Thu, 05 Mar 2009 10:23:58 GMT


  think you are getting yourself into a more and more tangled mess.  As a
fairly broad rule, you shouldn't be doing any state-changing behavior in
onSaveInstanceState() -- this is not for the system to tell you about
something interesting happening, but for it to get your current state at
whatever point it thinks it might need it.

Could we back up and look at exactly what you are trying to do? In which
situations do you want the dialog to stay, and in which do you want it to
disappear? This shouldn't be in terms of "when state is saved" or "when it
is destroyed", but "when the user flips the lid / changes the
configuration," "when the user presses home," "when the user switches to
another activity," etc.

On Wed, Mar 4, 2009 at 5:28 PM, Nmix <nepean...@gmail.com> wrote:



--
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support. All such questions should be posted on public
forums, where I and others can see and answer them.

--~--~---------~--~----~------------~-------~--~----~



Dialog Survival Over Configuration Change

by Romain Guy » Fri, 06 Mar 2009 13:14:13 GMT


 gt;> It is a problem. In my, and others', opinion it is a *bug* that the

It is a bug indeed.




--
Romain Guy
Android framework engineer
romain...@android.com

Note: please don't send private questions to me, as I don't have time
to provide private support. All such questions should be posted on
public forums, where I and others can see and answer them

--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. keunggulan android dari bb

Salam semua untuk android user..

Saya adalh orang awam yang baru menggunakan android,jadi saya belum
mengetahui benar apa sebarnya android..yg ingin saya tanyakan
adalahapa seh keunggulan dari android daripada bb??saya selalu
mempromosikan android kepada teman2 sya..namun ketika ditanya
keunggulan dari bb apa saya kurang mngerti..ehehe..mohon diberikan
penjelasannya agar sya bisa lanjut mempromosikab android kepda teman2
saya.. Salam..


-- 
===============

2. [Need your help!!]Automation test by using Monkey Runner

We know, A GUI automation testing tool -- monkey runner is there, it
provide some functions such as Keyboard function, input message
functions as well as touch, which are all very good supports for the
automation testing.

However, there seems somethings that puzzle me a lot, so search helps
from all of you here:
1. As in most of GUI automation testing, locate the objects in the
screen and judge the existing of the objects are very important, so is
there any way to implement this function, or can we extend the
function ourselves, if so, how?
2. Now we can't touch the object by provide name or id or any other
attributes of the objects but just touch on location(by X,Y). in
common GUI automation, it's very inflexible and bring much trouble to
users to get the location info. Is there any way to resolve this
problems? or any further plans for the enhancement?

-- 

3. OOT: WTA menonaktifkan RBT di Smart

4. [WTI] Lector 1.989.000 7" 2.1

5. Kecopetan Dell Streak Merah di Bandung

6. what does the mOMXLivesLocally in stagefright or OMXCodec used for?

7. View & Open files downloaded from the server