Well... managed dialogs are saved and restored in a map, and so if you have multiple ones displayed the order they are re-created won't be guaranteed to be the same. If you only have one displayed at a time you should be fine (and I would recommend only having one displayed anyway since it avoids having a bunch more resources used for displaying the ones behind on screen and a less cluttered looking UI).
On Fri, Dec 9, 2011 at 4:58 PM, Royston <[email protected]> wrote: > Dianne, > Thank you for the response. Can I infer from you answer that the behaviour > I have seen is as expected? I think I should have gone the DialogFragment > route from project inception but probably not a good solution at this > stage. I do note that if I consistently use removeDialog instead of > dismissDialog the problem is avoided. This takes away any benefit achieved > from Dialog caching but is a quick workaround for this situation. > > Regards > > > Roy > > -- > 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 > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
