commitAllowingStateLoss
2017-05-17 23:49
351 查看
使用commitAllowingStateLoss()函数原因:commit()函数和commitAllowingStateLoss()函数的唯一区别就是当发生状态丢失的时候,后者不会抛出一个异常。通常你不应该使用这个函数,因为它意味可能发生状态丢失。当然,更好的解决方案是commit函数确保在Activity的状态保存之前调用,这样会有一个好的用户体验。除非状态丢失的可能无可避免,否则就不应该使用commitAllowingStateLoss()函数。
相关文章推荐
- 源码分析commitAllowingStateLoss() 和commit()的区别(挑重点去知道)
- commitAllowingStateLoss()
- commit(), commitNow()和commitAllowingStateLoss()
- commitallowingstateloss 和commit的区别
- commit()和commitallowingstateloss()
- Android commit和commitAllowingStateLoss区别及应用场景
- commitAllowingStateLoss()
- FragmentTransaction的commit和commitAllowingStateLoss的区别
- 源码分析commitAllowingStateLoss() 和commit()的区别
- FragmentTransaction的commit和commitAllowingStateLoss的区别
- commitAllowingStateLoss()
- 加入第三方sdk后包冲突引起的找不到符号 commitNow() ,commitNowAllowingStateLoss()系列问题的解决
- Fragment commit 替换成 commitAllowingStateLoss()
- FragmentTransaction的commit和commitAllowingStateLoss的区别
- FragmentTransaction的commit和commitAllowingStateLoss的区别
- FragmentTransaction的commit和commitAllowingStateLoss的区别
- commitallowingstateloss 和commit的区别
- FragmentTransaction的commit和commitAllowingStateLoss的区别
- FragmentTransaction的commit和commitAllowingStateLoss的区别
- FragmentTransaction的commit和commitAllowingStateLoss的差别