Android   发布时间:2022-04-28  发布网站:大佬教程  code.js-code.com
大佬教程收集整理的这篇文章主要介绍了Android 中为什么要用Fragment.setArguments(Bundle bundle)来传递参数大佬教程大佬觉得挺不错的,现在分享给大家,也给大家做个参考。

Fragment在Android3.0开始提供,并且在兼容包中也提供了Fragment特性的支持。Fragment的推出让我们编写和管理用户界面更快捷更方便了。

但当我们实例化自定义Fragment时,为什么官方推荐Fragment.setArguments(Bundle bundlE)这种方式来传递参数,而不推荐通过构造方法直接来传递参数呢?为了弄清这个问题,我们可以做一个测试,分别测试下这两种方式的不同

首先,我们来测试下通过构造方法传递参数的情况

public class FramentTestActivity extends ActionBarActivity { 
  @Override 
  protected void onCreate(Bundle savedInstanceStatE) { 
    super.onCreate(savedInstanceStatE); 
    setContentView(R.layout.activity_main); 
    if (savedInstanceState == null) { 
      getSupportFragmentManager().begintransaction() 
          .add(R.id.container,new TestFragment("param")).commit(); 
    } 
  } 
  public static class TestFragment extends Fragment { 
    private String mArg = "non-param"; 
    public TestFragment() { 
      Log.i("INFO","TestFragment non-parameter constructor"); 
    } 
    public TestFragment(String arg){ 
      mArg = arg; 
      Log.i("INFO","TestFragment construct with parameter"); 
    } 
    @Override 
    public View onCreateView(LayoutInflater inflater,ViewGroup container,Bundle savedInstanceStatE) { 
      View rootView = inflater.inflate(R.layout.fragment_main,container,falsE); 
      TextView tv = (TextView) rootView.findViewById(R.id.tv); 
      tv.setText(mArg); 
      return rootView; 
    } 
  } 
} 

可以看到我们传递过来的数据正确的显示了,现在来一个问题,如果设备配置参数发生变化,这里以横竖屏切换来说明问题,显示如下

发生了什么问题呢?我们传递的参数哪去了?为什么会显示认值?不急着讨论这个问题,接下来我们来看看Fragment.setArguments(Bundle bundlE)这种方式的运行情况

public class FramentTest2Activity extends ActionBarActivity { 
    @Override 
    protected void onCreate(Bundle savedInstanceStatE) { 
       super.onCreate(savedInstanceStatE); 
       setContentView(R.layout. activity_main); 
       if (savedInstanceState == null) { 
          getSupportFragmentManager().begintransaction() 
                 .add(R.id. container,TestFragment.newInstance("param")).commit(); 
       } 
    } 
    public static class TestFragment extends Fragment { 
       private static final String ARG = "arg"; 
       public TestFragment() { 
          Log. i("INFO","TestFragment non-parameter constructor" ); 
       } 
       public static Fragment newInstance(String arg){ 
          TestFragment fragment = new TestFragment(); 
          Bundle bundle = new Bundle(); 
          bundle.putString( ARG,arg); 
          fragment.setArguments(bundlE); 
           return fragment; 
       } 
       @Override 
       public View onCreateView(LayoutInflater inflater,Bundle savedInstanceStatE) { 
          View rootView = inflater.inflate(R.layout. fragment_main,falsE); 
          TextView tv = (TextView) rootView.findViewById(R.id. tv); 
          tv.setText(getArguments().getString( ARG)); 
           return rootView; 
       } 
    } 
} 

我们再来看看横竖屏切换后的运行情况

看到了吧,我们传递的参数在横竖屏切换的情况下完好保存了下来,正确的显示用户
那么这到底是怎么回事呢,我们知道设备横竖屏切换的话,当前展示给用户的Activity认情况下会重新创建并展现给用户,那依附于Activity的Fragment会进行如何处理呢,我们可以通过源码来查看

先来看看Activity的onCreate(Bundle saveInstancE)方法

 protected void onCreate(Bundle savedInstanceStatE) { 
  if (DEBUG_LIFECYCLE ) Slog.v( TAG,"onCreate " + this + ": " + savedInstanceStatE); 
  if (mLastNonConfigurationInstances != null) { 
    mAllLoadeRMANagers = mLastNonConfigurationInstances .loaders ; 
  } 
  if (mActivityInfo .parentActivityName != null) { 
    if (mActionBar == null) { 
      mEnableDefaultActionBarUp = true ; 
    } else { 
      mActionBar .setDefaultDisplayHomeAsUpEnabled( truE); 
    } 
  } 
  if (savedInstanceState != null) { 
    Parcelable p = savedInstanceState.getParcelable( FRAGMENTS_TAG ); 
    mFragments .restoreAllState(p,mLastNonConfigurationInstances != null 
        ? mLastNonConfigurationInstances .fragments : null); 
  } 
  mFragments .dispatchCreate(); 
  getApplication().dispatchActivityCreated( this,savedInstanceStatE); 
  mCalled = true ; 
} 

由于我们的Fragment是由FragmentManager来管理,所以可以跟进FragmentManager.restoreAllState()方法,通过对当前活动的Fragmnet找到下面的代码

 for (int i=0; i<fms.mActive.length; i++) { 
      FragmentState fs = fms.mActive[i]; 
      if (fs != null) { 
       Fragment f = fs.instantiate(mActivity,mParent); 
        if (DEBUG) Log.v(tag,"restoreAllState: active #" + i + ": " + f); 
        mActive.add(f); 
        // Now that the fragment is instantiated (or came from being 
        // retained abovE),clear mInstance in case we end up re-restoring 
        // from this FragmentState again. 
        fs.mInstance = null; 
      } else { 
        mActive.add(null); 
        if (mAvailInDices == null) { 
          mAvailInDices = new ArrayList<Integer>(); 
        } 
        if (DEBUG) Log.v(tag,"restoreAllState: avail #" + i); 
        mAvailInDices.add(i); 
      } 
} 

接下来我们可以看看FragmentState.instantitate()方法的实现

public Fragment instantiate(Activity activity,Fragment parent) { 
    if (mInstance != null) { 
      return mInstance ; 
    } 
    if (mArguments != null) { 
      mArguments .setClassLoader(activity.getClassLoader()); 
    } 
    mInstance = Fragment.instantiate(activity,mClassName,mArguments ); 
    if (mSavedFragmentState != null) { 
      mSavedFragmentState .setClassLoader(activity.getClassLoader()); 
      mInstance .mSavedFragmentState = mSavedFragmentState ; 
    } 
    mInstance .seTindex(mIndex,parent); 
    mInstance .mFromLayout = mFromLayout ; 
    mInstance .mRestored = true; 
    mInstance .mFragmentId = mFragmentId ; 
    mInstance .mContainerId = mContainerId ; 
    mInstance .mTag = mTag ; 
    mInstance .mRetainInstance = mRetainInstance ; 
    mInstance .mDetached = mDetached ; 
    mInstance .mFragmentManager = activity.mFragments; 
    if (FragmentManagerImpl.DEBUG) Log.v(FragmentManagerImpl.TAG,"Instantiated fragment " + mInstance ); 
    return mInstance ; 
  } 

可以看到最终转入到Fragment.instantitate()方法

public static Fragment instantiate(Context context,String fname,Bundle args) { 
  try { 
    Class<?> clazz = sClassmap .get(fName); 
    if (clazz == null) { 
      // Class not found in the cache,see if it's real,and try to add it 
      clazz = context.getClassLoader().loadClass(fName); 
      sClassmap .put(fname,clazz); 
    } 
    Fragment f = (Fragment)clazz.newInstance(); 
    if (args != null) { 
      args.setClassLoader(f.getClass().getClassLoader()); 
      f. mArguments = args; 
    } 
    return f; 
  } catch (ClassnotFoundException E) { 
    throw new InstantiationException( "Unable to instantiate fragment " + fname 
        + ": make sure class name exists,is public,and has an" 
        + " empty constructor that is public",E); 
  } catch (java.lang.InstantiationException E) { 
    throw new InstantiationException( "Unable to instantiate fragment " + fname 
        + ": make sure class name exists,E); 
  } catch (illegalaccessexception E) { 
    throw new InstantiationException( "Unable to instantiate fragment " + fname 
        + ": make sure class name exists,E); 
  } 

通过此方法可以看到,最终会通过反射无参构造实例化一个新的Fragment,并且给mArgments初始化为原先的值,而原来的Fragment实例的数据都丢失了,并重新进行了初始化

通过上面的分析,我们可以知道Activity重新创建时,会重新构建它所管理的Fragment,原先的Fragment的字段值将会全部丢失,但是通过Fragment.setArguments(Bundle bundlE)方法设置的bundle会保留下来。所以尽量使用Fragment.setArguments(Bundle bundlE)方式来传递参数

以上所述是小编给大家介绍的Android 中为什么要用Fragment.setArguments(Bundle bundlE)来传递参数,希望对大家有所帮助,如果大家有任何疑问欢迎给我给我留言,小编会及时回复大家的!

大佬总结

以上是大佬教程为你收集整理的Android 中为什么要用Fragment.setArguments(Bundle bundle)来传递参数全部内容,希望文章能够帮你解决Android 中为什么要用Fragment.setArguments(Bundle bundle)来传递参数所遇到的程序开发问题。

如果觉得大佬教程网站内容还不错,欢迎将大佬教程推荐给程序员好友。

本图文内容来源于网友网络收集整理提供,作为学习参考使用,版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ:384754419,请注明来意。
标签:android参数