As far as I can tell, there are two ways to show a Dialog from an Activity.
AlertDialog.Builder
), and then call the newly created Dialog's show()
method.showDialog()
method, passing in an int that uniquely defines what sort of Dialog you want to build. Then override onCreateDialog()
to actually build the Dialog, and Android will display it for you.The second method seems to be the standard practice but I'm curious if there is any reason it matters which one I use. Here's all I can come up with:
Reasons to use Dialog.show
Activity.showDialog
, as described in this question. You may have to store a String or something in a member variable, just so that it can be retrieved moments later during onCreateDialog
or onPrepareDialog
.showDialog()
switch
statement in the overridden onCreateDialog
methodswitch
statement in the overridden onPrepareDialog
methodReasons to use Activity.showDialog
:
Activity.showDialog
say that the Dialog is "managed" by the Activity which I suppose provides some benefit? But this is also true if you use the AlertDialog.Builder
, I would think, because you pass in this
as an argument to the Builder's constructor. So my question is, what are the criteria for deciding when to use Activity.showDialog
and when to use Dialog.show
, and why?
In my opinion you should prefer showDialog
because this method will do most of the work for you. In example You don't have to worry that you will lose reference to your dialog after changing screen orientation. It will be recreated automatically. Dialog.show
is much more prone to errors.
So I suggest you to use showDialog
everywhere you can.