DialogFragment is a cleaner way to do this, putting all of the dialog related code in a separate class instead of callbacks on Activity. You can use this with the fragment compat library on older platforms. You still can't do a blocking call to wait a result, however; your activity will need to have a separate callback to receive the result.
On Tue, May 3, 2011 at 1:47 PM, TreKing <[email protected]> wrote: > On Mon, May 2, 2011 at 9:08 AM, GerhardS <[email protected]> wrote: > >> Any suggestions? > > > Not really, unfortunately. I think the Android dialog scheme is as it is on > purpose, though I too am not a fan. I think some things have changed with > 3.0 with DialogFragments from reading this forum, but I have not > investigated this myself. Might be worth looking into. > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > > -- > 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
