转:http://blog.csdn.net/hitlion2008/article/details/7567549#t0

Dialog是任何系统都必须有的一个控件,作为辅助窗口,用于显示一些消息,或请求用户采取一引起操作等。

在Android中也不例外,基本使用可能参看文档。

使用时的注意事项

1. BACK键能取消掉对话框(dismiss),但是却不会触发其onOkey和onCancel回调接口,所以如果你的对话框会改某些状态,一定要注意还有第三种方式取消对话框。

2. 尽量少用模态对话框(Model
dialog),如果Dialog.setCancellable(false),就变成了一个模态对话框,除了程序内部把其Dismiss,否则按什么
键都无法将其取消。这是极差的用户体验,对话框本身就是一种干扰,再无法取消会把用户搞疯的。所以除非特别有必要,也即当执行某个操作时不希望被打破,才
可以使用模态对话框。

3. 尽量少用对话框,它对用户是一种干扰,除非需要用户做操作,或者做出选择。通常的一般性的通知用Toast或者Notification就足够了。

4.
不要使用对话框风格的Activity,也即把Activity变成一个对话框。因为这样是自已定义的布局,与系统Dialog的风格可能会不一致。最严
重的是当系统风格发生变化,Dialog的子类会变化,但Activity式的对话框就不会变化。可以在ICS中找一找Activity对话框,你会发现
其OK是在左边,而ICS中系统Dialog的OK都是在右边的。

5. 尽量保证Dialog对象活在Activity的生命周期之内,也即至多是在onCreate()和onDestroy()之间。

6.
要想到和测试到Activity在其Dialog.dismiss()之前死掉的情况。因为Activity必须依附于某个正在显示的Activity实
例,当显示和取消的时候其Activity实例必须存在,否则就会有"IllegalArgumentException: View not
attached to window manager"。

05-15 02:45:26.320: E/AndroidRuntime(1161): java.lang.IllegalArgumentException: View not attached to window manager
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.view.WindowManagerImpl.findViewLocked(WindowManagerImpl.java:355)
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.view.WindowManagerImpl.removeView(WindowManagerImpl.java:200)
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.view.Window$LocalWindowManager.removeView(Window.java:432)
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.app.Dialog.dismissDialog(Dialog.java:278)
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.app.Dialog.access$000(Dialog.java:71)
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.app.Dialog$1.run(Dialog.java:111)
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.app.Dialog.dismiss(Dialog.java:268)
05-15 02:45:26.320: E/AndroidRuntime(1161): at com.hilton.effectiveandroid.app.DialogDemo$1.handleMessage(DialogDemo.java:26)
05-15 02:45:26.320: E/AndroidRuntime(1161): at android.os.Handler.dispatchMessage(Handler.java:99)

7. Dialog.show()必须在主线程里调用,但Dialog.dismiss()却可以在任何线程中调用。

三种使用方式比较

1. 直接创建一个局部的Dialog对象

优点是变量是局部的容易理解和维护。缺点是Dialog对象难以控制,容易引发RuntimeException。

2. 把Dialog对象变成Activity的域

优点是Dialog对象可以重复利用,且Activity可以控制以保证Dialog不会在Activity生命周期外显示。是推荐的使用方式。

3. 用Activity的方法onCreateDialog(), showDialog()和dismissDialog()

优点是Frameworks会帮忙照看Dialog,在大多数情况下这是推荐的做法。但是对于Activity提前死掉的情况,此方法必有RuntimeException,且无法回避。

实例

public class DialogDemo extends Activity {
private static final int DISMISS_DIALOG = 1; private ProgressDialog mBetterDialog; private Handler mMainHandler = new Handler() {
@Override
public void handleMessage(Message msg) {
switch (msg.what) {
case DISMISS_DIALOG:
Dialog dialog = (Dialog) msg.obj;
dialog.dismiss();
break;
default:
break;
}
}
};
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.dialog_demo); final Button sucking = (Button) findViewById(R.id.sucking);
sucking.setOnClickListener(new View.OnClickListener() {
public void onClick(View v) {
final Activity activity = DialogDemo.this;
final ProgressDialog dialog = new ProgressDialog(activity);
dialog.setTitle("Worst dialogging");
dialog.setMessage("This is the worst dialogging scheme, NEVER use it. This dialog is easy to " +
"run out of its attached activity, yielding WindowManager#BadTokenException if the activity is gone when dismissing");
dialog.setIndeterminate(true);
dialog.setCancelable(true);
// You MUST do the show in main thread anyway
dialog.show();
new Thread(new Runnable() {
public void run() {
SystemClock.sleep(10000);
/*
* IllegalArgumentException: View not attached to window manager
* If the activity showing the dialog was killed before dismiss() out of rotation or locale changed,
* the dialog will gone with activity, but when dismiss() yields "IllegalArgumentException: View not attached to
* window manager".
* Checking isShowing() won't help.
* Checking activity.isFinishing() won't help, either.
* Dismiss it in main thread also won't give any help.
*/
// THIS WON't WORK
// if (dialog.isShowing()) {
// dialog.dismiss();
// }
// if (!activity.isFinishing()) {
// dialog.dismiss();
// }
Message msg = Message.obtain();
msg.what = DISMISS_DIALOG;
msg.obj = dialog;
mMainHandler.sendMessage(msg);
}
}).start();
}
}); final Button better = (Button) findViewById(R.id.better);
better.setOnClickListener(new View.OnClickListener() {
public void onClick(View v) {
mBetterDialog = new ProgressDialog(DialogDemo.this);
mBetterDialog.setTitle("Better dialogging");
mBetterDialog.setMessage("This dialogging can be used. The dialog object is a field of its activity, so activity can" +
" control it to make sure dialog only lives within activity lifecircle");
mBetterDialog.setIndeterminate(true);
mBetterDialog.setCancelable(true);
// You MUST do the show in main thread anyway
mBetterDialog.show();
new Thread(new Runnable() {
public void run() {
SystemClock.sleep(10000);
/*
* This is much better, mBetterDialog is a field of its activity, so activity can take care of it in order
* to make sure dialog only live within activity's life circle, to avoid any unexpected exceptions.
*/
// THIS really works
if (mBetterDialog != null && mBetterDialog.isShowing()) {
mBetterDialog.dismiss();
}
}
}).start();
}
}); final Button optional = (Button) findViewById(R.id.optional);
optional.setOnClickListener(new View.OnClickListener() {
@SuppressWarnings("deprecation")
public void onClick(View v) {
showDialog(0);
new Thread(new Runnable() {
public void run() {
SystemClock.sleep(10000);
/*
* This way works best for most of time, except if activity died before dismissing, exception must be
* thrown: "IllegalArgumentException: View not attached to window manager".
* Although activity takes care of its belonging dialog, there is no way to operate it manually any more.
* First you do not have reference to dialog object and second, any manual operation only interferences
* and breaks state maintained by frameworks.
*/
dismissDialog(0);
}
}).start();
}
});
} @Override
protected Dialog onCreateDialog(int id) {
ProgressDialog d = new ProgressDialog(this);
d.setTitle("Optional dialogging");
d.setMessage("This dialogging scheme works best for most times, the dialogs are all taken care of by activitys and frameworks" +
". Except for activity being killed during dialog showing");
d.setIndeterminate(true);
d.setCancelable(true);
return d;
} @Override
protected void onDestroy() {
super.onDestroy();
// Activity is dying, all its belonging dialogs should be dismissed, of course.
if (mBetterDialog != null && mBetterDialog.isShowing()) {
mBetterDialog.dismiss();
mBetterDialog = null;
}
// For dialogs showed via showDialog(int), no way to stop it in onDestroy()
// dismissDialog(0); // cause "IllegalArgumentException: no dialog with id 0 was ever shown via Activity#showDialog"
// This is because Activity has to manage its dialog during onPause() and onResume() to restore
// dialogs' state. So if you manually dismiss it in onDestroy(), it will cause JE. // removeDialog(0);// cause "IllegalArgumentException: no dialog with id 0 was ever shown via Activity#showDialog", when
// dismissing in thread.
// This is because Activity has to manage its dialog during onPause() and onResume() to restore
// dialogs' state. So if you manually dismiss it in onDestroy(), it will cause JE.
}
}

Android实战技巧:Dialog (转)的更多相关文章

  1. Android实战技巧:深入解析AsyncTask

    AsyncTask的介绍及基本使用方法 关于AsyncTask的介绍和基本使用方法可以参考官方文档和Android实战技巧:多线程AsyncTask这里就不重复. AsyncTask引发的一个问题 上 ...

  2. Android实战技巧之十二:Android Studio导入第三方类库、jar包和so库

    第三方类库源码 将一网友的XMPP代码从ADT转到AS时,发现其使用了第三方类库,源码放在了lib下,直接在AS中Import project,第三方类库并没有自动导入进来,看来需要自己动手了. 项目 ...

  3. Android实战技巧:ViewStub的应用

    在开发应用程序的时候,经常会遇到这样的情况,会在运行时动态根据条件来决定显示哪个View或某个布局.那么最通常的想法就是把可能用到的View都写在上面,先把它们的可见性都设为View.GONE,然后在 ...

  4. Android实战技巧之六:PreferenceActivity使用详解

    一.写作前面 当我们做应用的时候,需要用户配置一些信息,而这就是通常所说的应用设置. 对于Android系统来说,系统本身的设置带来的用户体验和习惯已经深入人心,在我们的应用中同样用到类似的设置页, ...

  5. Android实战技巧之十九:android studio导出jar包(Module)并获得手机信息

    AS中并没有独立的Module 工程,可是能够在普通的Project中增加Module.所谓的Module就是我们通常所指的模块化的一个单元.并经常以jar包的形式存在.以下以一个获取手机信息的样例演 ...

  6. Android实战技巧: ListView之ContextMenu无法弹出

    问题 Activity中使用了ListView作为布局.当每一列表项中含有默认能获取焦点的子View时有可能会对ListView的某些事件有影响: 1. OnItemClick 2. OnItemLo ...

  7. 【转】Android实战技巧之四十九:Usb通信之USB Host

    零 USB背景知识 USB是一种数据通信方式,也是一种数据总线,而且是最复杂的总线之一. 硬件上,它是用插头连接.一边是公头(plug),一边是母头(receptacle).例如,PC上的插座就是母头 ...

  8. Android实战技巧:如何在ScrollView中嵌套ListView

    前几天因为项目的需要,要在一个ListView中放入另一个ListView,也即在一个ListView的每个ListItem中放入另外一个ListView.但刚开始的时候,会发现放入的小ListVie ...

  9. Android实战技巧之三十八:Handler使用中可能引发的内存泄漏

    问题描写叙述 曾几何时,我们用原来的办法使用Handler时会有以下一段温馨的提示: This Handler class should be static or leaks might occur ...

随机推荐

  1. hdu2182Frog(动态规划)

    Problem Description A little frog named Fog is on his way home. The path's length is N (1 <= N &l ...

  2. MySQL replace into 与insert into

    https://blog.csdn.net/helloxiaozhe/article/details/77427266 使用replace带来的问题 1.Replace into 操作在唯一键重复情况 ...

  3. c#处理json格式类型的字符串

    string channelGroup=[{"SpType":"1","BaseInfoId":["xxx"," ...

  4. Caused by: java.lang.ClassNotFoundException: com.alibaba.dubbo.common.Version

    <dependency> <groupId>com.alibaba.boot</groupId> <artifactId>dubbo-spring-bo ...

  5. win10下装win7双系统安装教程

    win10下装win7双系统安装教程 来源:www.laomaotao.org 时间:2017-02-13 10:15 新买的电脑预装了win10系统,但win10对于有些游戏兼容性不是很好,总是会出 ...

  6. spring-第十四篇之资源访问Resource接口

    1.Resource接口提供的主要方法 1>getInputStream():定位并打开资源,返回资源对应的输入流.每次调用都返回新的输入流.调用者必须负责关闭输入流. 2>isOpen( ...

  7. Hibernate使用时需要注意的几个小问题

    今天晚上玩了一下JDBC连接数据库,之后又利用Hibernate进行了数据库的访问,感觉利用Hibernate对数据库访问在文件配置好了之后确实更加简单快捷. 但是在操作的过程中也有一些细节需要注意一 ...

  8. P3826 [NOI2017]蔬菜

    传送门 注意每一单位蔬菜的变质时间是固定的,不随销售发生变化 固定的...... 就是每一个单位的蔬菜在哪一天变质是早就定好了的 发现从第一天推到最后一天很不好搞 考虑反过来,从最后一天推到第一天,这 ...

  9. 69.Daily Temperatures(日常气温)

    Level:   Medium 题目描述: Given a list of daily temperatures T, return a list such that, for each day in ...

  10. MVC路由学习:自定义路由参数(用户看不到参数名),重新定义路由规则

    MVC路由:由于路由global中注册了,在程序第一次运行时,在MVC会自动生成路由,类似于字典的格式缓存下来,但路由生成的规则又是怎样的呢? 路由生成规则是: 1>更具你定义的的顺序查找路由规 ...