Fragment强烈不推荐使用自定义带参的构造函数
来源:互联网 发布:php strcasecmp 编辑:程序博客网 时间:2024/05/14 04:14
原文链接:http://blog.csdn.net/y_lang/article/details/41694287
项目在运行monkey63小时左右,出现9次CRASH:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.aliyun.easylauncher/com.aliyun.easylauncher.dialpad.PhoneRecordActivity}: android.support.v4.app.Fragment$InstantiationException: Unable to instantiate fragment com.aliyun.easylauncher.dialpad.DialFragment: make sure class name exists, is public, and has an empty constructor that is public
正常的使用一切都是正常,Google后发现,Fragment有下面的注意事项:
public Fragment ()
Default constructor. Every fragment must have an empty constructor, so it can be instantiated when restoring its activity's state. It is strongly recommended that subclasses do not have other constructors with parameters, since these constructors will not be called when the fragment is re-instantiated; instead, arguments can be supplied by the caller with setArguments(Bundle)
and later retrieved by the Fragment withgetArguments()
.
Applications should generally not implement a constructor. The first place application code an run where the fragment is ready to be used is in onAttach(Activity)
, the point where the fragment is actually associated with its activity. Some applications may also want to implementonInflate(Activity, AttributeSet, Bundle)
to retrieve attributes from a layout resource, though should take care here because this happens for the fragment is attached to its activity.
394 public static Fragment instantiate(Context context, String fname, Bundle args) {
395 try {
396 Class<?> clazz = sClassMap.get(fname);
397 if (clazz == null) {
398 // Class not found in the cache, see if it's real, and try to add it
399 clazz = context.getClassLoader().loadClass(fname);
400 sClassMap.put(fname, clazz);
401 }
402 Fragment f = (Fragment)clazz.newInstance(); //问题出在这里
403 if (args != null) {
404 args.setClassLoader(f.getClass().getClassLoader());
405 f.mArguments = args;
406 }
407 return f;
408 } catch (ClassNotFoundException e) {
409 throw new InstantiationException("Unable to instantiate fragment " + fname
410 + ": make sure class name exists, is public, and has an"
411 + " empty constructor that is public", e);
412 } catch (java.lang.InstantiationException e) {
413 throw new InstantiationException("Unable to instantiate fragment " + fname
414 + ": make sure class name exists, is public, and has an"
415 + " empty constructor that is public", e);
416 } catch (IllegalAccessException e) {
417 throw new InstantiationException("Unable to instantiate fragment " + fname
418 + ": make sure class name exists, is public, and has an"
419 + " empty constructor that is public", e);
420 }
421
解决方案(来自stackoverflow),原文链接: http://stackoverflow.com/questions/10450348/do-fragments-really-need-an-empty-constructor
You shouldn't really be overriding the constructor anyway. You should have a newInstance()
static method defined and pass any parameters via arguments (bundle)
For example:
public static final AlertFragment newInstance(int title, String message){ AlertFragment f = new AlertFragment(); Bundle bdl = new Bundle(2); bdl.putInt(EXTRA_TITLE, title); bdl.putString(EXTRA_MESSAGE, message); f.setArguments(bdl); return f;}
And of course grabbing the args this way:
@Overridepublic void onCreate(Bundle savedInstanceState){ title = getArguments().getInt(EXTRA_TITLE); message = getArguments().getString(EXTRA_MESSAGE); //... //etc //...}
Then you would instantiate from your fragment manager like so:
public onCreate(Bundle savedInstanceState) { if(savedInstanceState == null){ getSupportFragmentManager() .beginTransaction() .replace(R.id.content,AlertFragment.newInstance( R.string.alert_title, "Oh noes an error occured!") ) .commit(); }}
This way if detached and re-attached the object state can be stored through the arguments. Much like bundles attached to Intents.
- Fragment强烈不推荐使用自定义带参的构造函数
- Fragment强烈不推荐使用自定义带参的构造函数
- Fragment强烈不推荐使用自定义带参的构造函数
- Fragment强烈不推荐使用自定义带参的构造函数
- Fragment不推荐使用自定义带参的构造函数
- Fragment使用带参数的构造函数遇到的问题
- 为什么我强烈不推荐ASM环境下使用ASMLIB
- Qt 带自定义参数的构造函数
- Fragment强烈要求构造方法为空
- Fragment的构造函数
- Fragment的构造函数
- 三角形类的构造函数-使用带参数构造函数
- 5.1多线程使用(不带参数的构造函数进行定义多线程)
- 五周 项目1 三角形类的构造函数 .1使用带参构造函数
- 第五周项目一使用带参构造函数,三角形类的构造函数
- 黑白棋(落子)绞尽脑汁 与老师模式强烈不兼容的思路(不推荐)
- 强烈不推荐使用flipper实现左右滑动动画显示结果
- 如何在SpringBoot中使用JSP ?但强烈不推荐,果断改Themeleaf吧
- solr4.9.1索引导入http远程doc文件
- Spring-Java事物回滚失效处理
- MySQL索引背后的数据结构及算法原理
- 论IT行业青春饭
- 回文串问题(2013中南大学研究生复试题)
- Fragment强烈不推荐使用自定义带参的构造函数
- 设置自定义UITableViewCell之间的间距
- 啊哈磊的算法
- java嵌套类(Nested Classes)总结
- HDU 1385:Minimum Transport Cost【Floyd】
- php中数据库pdo的exec方法返回影响行数的问题
- nginx + tomcat 负载均衡+session复制共享
- POJ 2785 折半枚举
- 编译fdk-aac,执行批处理的时候出现这个错误,mingw32-gcc.exe: error: CreateProcess: No such file or directory的问题