我的活动正在尝试创建一个AlertDialog,它需要一个上下文作为参数。如果我使用:

AlertDialog.Builder builder = new AlertDialog.Builder(this);

然而,我对使用“this”作为上下文持怀疑态度,因为即使在屏幕旋转这样简单的操作中,Activity被破坏和重新创建时,也有可能发生内存泄漏。来自Android开发者博客的相关文章:

There are two easy ways to avoid context-related memory leaks. The most obvious one is to avoid escaping the context outside of its own scope. The example above showed the case of a static reference but inner classes and their implicit reference to the outer class can be equally dangerous. The second solution is to use the Application context. This context will live as long as your application is alive and does not depend on the activities life cycle. If you plan on keeping long-lived objects that need a context, remember the application object. You can obtain it easily by calling Context.getApplicationContext() or Activity.getApplication().

但是对于AlertDialog(), getApplicationContext()或getApplication()都不能作为上下文,因为它会抛出异常:

"无法添加窗口-令牌null不是用于应用程序"

参考文献:1、2、3等。

所以,这真的应该被认为是一个“bug”,因为我们被正式建议使用Activity.getApplication(),但它并没有像宣传的那样发挥作用?

Jim


当前回答

使用这个对我不起作用,但是MyActivityName。这做。

其他回答

如果你的对话框是在适配器上创建的:

将活动传递给适配器构造函数:

adapter = new MyAdapter(getActivity(),data);

适配器接收:

 public MyAdapter(Activity activity, List<Data> dataList){
       this.activity = activity;
    }

现在你可以使用你的建造者

            AlertDialog.Builder alert = new AlertDialog.Builder(activity);

*****版本*****

您应该传递this@YourActivity而不是applicationContext或baseContext

使用MyDialog md = new MyDialog(MyActivity.this.getParent());

使用这个对我不起作用,但是MyActivityName。这做。

对于以后的读者,这应该有帮助:

public void show() {
    if(mContext instanceof Activity) {
        Activity activity = (Activity) mContext;
        if (!activity.isFinishing() && !activity.isDestroyed()) {
            dialog.show();
        }
    }
}