The method showDialog(int) from the type Activity is deprecated in android?

Question

The method showDialog(int) from the type Activity is deprecated.

bubuko.com,布布扣

What‘s the reason? and how to solve it?

PJL · Accepted Answer · 2011-11-02 12:41:34Z

Yes use DialogFragment and in onCreateDialog you can simply use an AlertDialog builder anyway to create a simple AlertDialog with Yes/No confirmation buttons. Not very much code at all.

With regards handling events in your fragment there would be various ways of doing it but I simply define a message Handler in my Fragment, pass it into the DialogFragment via its constructor and then pass messages back to my fragment‘s handler as approprirate on the various click events. Again various ways of doing that but the following works for me.

In the dialog hold a message and instantiate it in the constructor:

private Message okMessage;
...
okMessage = handler.obtainMessage(MY_MSG_WHAT, MY_MSG_OK);

Implement the `onClickListener‘ in your dialog and then call the handler as appropriate:

public void onClick(.....
    if (which == DialogInterface.BUTTON_POSITIVE) {
        final Message toSend = Message.obtain(okMessage);
        toSend.sendToTarget();
    }
 }

Edit

And as Message is parcelable you can save it out in onSaveInstanceState and restore it

outState.putParcelable("okMessage", okMessage);

Then in onCreate

if (savedInstanceState != null) {
    okMessage = savedInstanceState.getParcelable("okMessage");
}

How do you persist okMessage? The problem is that when the activity is restarted (orientation change or whatever), your custom constructor is not called and thus your okMessage will be null. – hrnt Nov 2 ‘11 at 11:59 — hrnt, Nov 2 ‘11 at 11:59
The problem is not okMessage - the problem is okMessage‘s target which will be null if you load it from a Bundle. If the target of a Message is null, and you use sendToTarget, you will get a NullPointerException - not because the Message is null, but because its target is. – hrnt Nov 2 ‘11 at 12:44 — hrnt, Nov 2 ‘11 at 12:44
Why We should be using DialogFragment instead of plain Dialogs ????? – Amit Nov 10 ‘12 at 7:03 — Amit, Nov 10 ‘12 at 7:03
What the advantages of using DialogFragment instead of a Dialog? – Raphael Petegrosso Dec 7 ‘12 at 14:43 — Raphael Petegrosso, Dec 7 ‘12 at 14:43
The advantage of using a DialogFragment is that all the life cycle of the dialog will be handled for you. You will never get the error ‘dialog has leaked...‘ again. Go to DialogFragment and forget Dialogs. – Snicolas Mar 13 ‘13 at 10:06 — Snicolas, Mar 13 ‘13 at 10:06

hrnt · Answer 2 · 2011-12-19 11:23:16Z

I would recommend using DialogFragment.

Sure, creating a "Yes/No" dialog with it is pretty complex considering that it should be rather simple task, but creating a similar dialog box with Dialog is surprisingly complicated as well.

(Activity lifecycle makes it complicated - you must let Activity manage the lifecycle of the dialog box - and there is no way to pass custom parameters e.g. the custom message to Activity.showDialog if using API levels under 8)

The nice thing is that you can usually build your own abstraction on top of DialogFragment pretty easily.

How you will handle alert dialog callbacks (yes, no)? – Alexey Zakharov Nov 2 ‘11 at 8:49 — Alexey Zakharov, Nov 2 ‘11 at 8:49
The easiest way would be to implement a method in the hosting Activity that takes a String parameter. When the user clicks "Yes", for example, the dialog calls the Activity‘s method with parameter "agree". These parameters are specified when showing the dialog, for example AskDialog.ask("Do you agree to these terms?", "agree", "disagree"); – hrnt Nov 2 ‘11 at 8:54 — hrnt, Nov 2 ‘11 at 8:54
But i need callback inside fragment, not activity. I can use setTargetFragment and cast it to interface. But it is hell. – Alexey Zakharov Nov 2 ‘11 at 8:59 — Alexey Zakharov, Nov 2 ‘11 at 8:59
You could also fetch the target fragment by setting a tag to the target and using FragmentManager‘s findFragmentByTag. But yeah, it requires a fair bit of code. – hrnt Nov 2 ‘11 at 9:53 — hrnt, Nov 2 ‘11 at 9:53

user1281750 · Answer 3 · 2013-06-14 23:27:09Z

Use DialogFragment over AlertDialog:

Since the introduction of API level 13:

the showDialog method from Activity is deprecated. Invoking a dialog elsewhere in code is not advisable since you will have to manage the the dialog yourself (e.g. orientation change).
Difference DialogFragment - AlertDialog

Are they so much different? From Android reference regarding DialogFragment:

A DialogFragment is a fragment that displays a dialog window, floating on top of its activity‘s window. This fragment contains a Dialog object, which it displays as appropriate based on the fragment‘s state. Control of the dialog (deciding when to show, hide, dismiss it) should be done through the APIhere, not with direct calls on the dialog.
Other notes
- Fragments are a natural evolution in the Android framework due to the diversity of devices with different screen sizes.
- DialogFragments and Fragments are made available in the support library which makes the class usable in all current used versions of Android.

ashishduh · Answer 4 · 2014-01-09 22:57:23Z

You can create generic DialogFragment subclasses like YesNoDialog and OkDialog, and pass in title and message if you use dialogs a lot in your app.

public class YesNoDialog extends DialogFragment
{
    public YesNoDialog()
    {

    }

    @Override
    public Dialog onCreateDialog(Bundle savedInstanceState)
    {
        Bundle args = getArguments();
        String title = args.getString("title", "");
        String message = args.getString("message", "");

        return new AlertDialog.Builder(getActivity())
            .setTitle(title)
            .setMessage(message)
            .setPositiveButton(android.R.string.yes, new DialogInterface.OnClickListener()
            {
                @Override
                public void onClick(DialogInterface dialog, int which)
                {
                    getTargetFragment().onActivityResult(getTargetRequestCode(), Activity.RESULT_OK, null);
                }
            })
            .setNegativeButton(android.R.string.no, new DialogInterface.OnClickListener()
            {
                @Override
                public void onClick(DialogInterface dialog, int which)
                {
                    getTargetFragment().onActivityResult(getTargetRequestCode(), Activity.RESULT_CANCELED, null);
                }
            })
            .create();
    }
}

Then call it using the following:

    DialogFragment dialog = new YesNoDialog();
    Bundle args = new Bundle();
    args.putString("title", title);
    args.putString("message", message);
    dialog.setArguments(args);
    dialog.setTargetFragment(this, YES_NO_CALL);
    dialog.show(getFragmentManager(), "tag");

And handle the result in onActivityResult.

can it work after activity being recreated (screen rotated) – Malachiasz Jan 30 at 10:22 — Malachiasz, Jan 30 at 10:22
Yes, DialogFragment handles all lifecycle events for you. – ashishduh Jan 30 at 14:45 — ashishduh, Jan 30 at 14:45
I think it doesn‘t because after rotation old Dialog still exists and it keeps assignent to old not existing fragment (dialog.setTargetFragment(this, YES_NO_CALL);) so after rotation getTargetFragment().onActivityResult doesn‘t work – Malachiasz Jan 30 at 15:21 — Malachiasz, Jan 30 at 15:21
I use this code for all my dialogs and they work fine when screen is rotated. setTargetFragment uses FragmentManager methods to retain state of Fragments. – ashishduh Jan 30 at 19:32 — ashishduh, Jan 30 at 19:32
I think that only way for it to work is to have the Fragment setRetainInstance(true) or (Activity not being destroyed). And this is unwanted in many cases. – Malachiasz Feb 3 at 10:20 — Malachiasz, Feb 3 at 10:20

The method dismissDialog(int) from the type Activity is deprecated

The method showDialog(int) from the type Activity is deprecated in android?

Android DialogFragment vs Dialog

4 Answers

Use DialogFragment over AlertDialog: