When onCreateDialogView is called, the Runnable is assigned a value. This Runnable object is actually created in a method call in the custom view subclass itself. This class stores a dialog variable. The Runnable will show the dialog if it is both not null and not showing. This condition happens after a call to onRestoreInstanceState with data indicating that the dialog was open - it will create a new dialog and assign it to this variable, but not show it.
On Saturday, November 2, 2013 5:49:59 PM UTC-4, TreKing wrote: > > > On Sat, Nov 2, 2013 at 1:37 PM, Michael Palmer > <[email protected]<javascript:> > > wrote: > >> So, I devised a workaround. In my DialogPreference subclass, a Runnable >> variable is stored. I overrode showDialog so that it first calls the >> superclass onShowDialog, and then calls the Runnable if it's not null. The >> Runnable calls a method that may launch the second dialog if necessary. >> However, using this workaround, the dialogs are *still* appearing in the >> wrong order. >> > > How are you using this Runnable? > > > ------------------------------------------------------------------------------------------------- > 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
