我有一个android.support.v7.app.ActionBarActivity
FrameLayout
持有SupportMapFragment
和android.support.v4.app.ListFragment
。
我在ActionBarActivity
if(mFM.findFragmentByTag("ListFragment")==null){
mPlaceListFragment = new PlaceListFragment_1();
mFM.beginTransaction().add(R.id.listfragment_container, mPlaceListFragment,"ListFragment").commit();
}else{
mPlaceListFragment = (PlaceListFragment_1)mFM.findFragmentByTag("ListFragment");
}
if(mFM.findFragmentByTag("MapFragment")==null){
mMapFragment = new map_fragment(); //always create map fragment
mFM.beginTransaction().add(R.id.mapfragment_container, mMapFragment,"MapFragment").commit();
}else{
mMapFragment = (map_fragment) mFM.findFragmentByTag("MapFragment");
}
为了避免在选择每个片段时重新创建它,我会根据选择的片段隐藏/显示它们。
@Override
public boolean onNavigationItemSelected(int i, long l) { //OnFragmentInteractionListener
FragmentTransaction ft = mFM.beginTransaction();
if(i==0){
//map
if (mPlaceListFragment.isVisible())ft.hide(mPlaceListFragment);
if (mMapFragment.isHidden())ft.show(mMapFragment);
}else{
//list
if (mPlaceListFragment.isHidden())ft.show(mPlaceListFragment);
if (mMapFragment.isVisible())ft.hide(mMapFragment);
}
ft.commit();
return true; //True if the event was handled, false otherwise.
}
一切正常。我可以使用ActionBar
中的下拉菜单选择每个片段并操纵UI等。方向更改也可以正常工作。
当ListFragment
可见且应用程序打开新活动并按下后退键以返回到原始活动时,会出现此问题。
OR
可以看到ListFragment并按下HOME按钮,并尝试从任务栏重新打开应用程序。
地图片段只是ListFragment不会出现问题。此应用程序适用于API17 +的 应用程序返回ListFragment确定,但UI控件(操作栏控件和活动下拉列表等)没有响应,屏幕消失并变得无响应。 没有LogCat错误。 它似乎是API10的问题,并在返回ListFragment时发生? 覆盖ActionBarActivity 这个问题发布了一段时间后我提出了同样的问题:Back button very slow @Override
protected void onResume() {
//activity - after onstart
super.onResume();
if(mAdView!=null) mAdView.resume();
FragmentTransaction ft = mFM.beginTransaction();
if(getSupportActionBar().getSelectedNavigationIndex()==0){
//show map
ft.show(mMapFragment);
ft.hide(mPlaceListFragment);
}else{
//show ListFragment
ft.show(mPlaceListFragment);
ft.hide(mMapFragment);
}
ft.commit();
}
@Override
protected void onPause() {
//activity
if(mAdView!=null) mAdView.pause();
super.onPause();
}
@Override
protected void onStop() {
super.onStop();
// If the client is connected
if (mLocationClient!=null && mLocationClient.isConnected()) {
/*
* Remove location updates for a listener.
* The current Activity is the listener, so
* the argument is "this".
*/
mLocationClient.removeLocationUpdates(this);
mLocationClient.disconnect();
}
EasyTracker.getInstance(this).activityStop(this);//put as last statement
}
@Override
protected void onDestroy() {
//activity
if(mAdView!=null) mAdView.destroy();
super.onDestroy();
//clean the file cache when root activity exit
//the resulting total cache size will be less than 3M
if(isTaskRoot()){
AQUtility.cleanCacheAsync(this);
}
if (mLocationClient !=null && !mLocationClient.isConnected()) mLocationClient.disconnect();
}
********************************************************************
//All handlers are set in Oncreate of main ActionBarActivity e.g.
//ActionBar Spinner
********************************************************************
if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.HONEYCOMB){
mSpinnerAdapter = ArrayAdapter.createFromResource(actionBar.getThemedContext(), R.array.action_list, android.R.layout.simple_spinner_dropdown_item);
}else{
mSpinnerAdapter = ArrayAdapter.createFromResource(actionBar.getThemedContext(), R.array.action_list, android.R.layout.simple_spinner_dropdown_item);
//mSpinnerAdapter = ArrayAdapter.createFromResource(actionBar.getThemedContext(), R.array.action_list, R.layout.navigation_spinner_item);
}
actionBar.setListNavigationCallbacks(mSpinnerAdapter, this);
********************************************************************
//other spinners and views belonging to main activity
********************************************************************
mSprSavedPlaces = (Spinner) findViewById(R.id.spr_saved_places);
mSprSavedPlaces.setOnItemSelectedListener(new AdapterView.OnItemSelectedListener() {
public void onItemSelected(AdapterView<?> parent, View view, int pos, long id) {
//stuff
}
//Also the Map and List fragments are repopuplated from via the main
//ActionBarActivity’s onSaveInstanceState and onRestoreInstanceState
//this seems to work ok.
答案 0 :(得分:0)
最后我找到了解决这个问题的方法。总之,在SupportMapFragment和ListFragment之间切换时出现问题。 FragmentTransaction类的隐藏/显示方法用于在存储在单个FrameLayout中的两个片段之间切换。但是,如果SupportMapFragment处于隐藏状态并且控制权被传递给新活动并再次返回,那么将会出现很大的延迟,并且UI将无法响应。
如果SupportMapFragment可见,则没有问题。这只发生在Android 2.3.3(三星Galaxy)手机上,运行HoneyComb +的模拟器没有问题
请参阅下面的解决方案说明和代码:
/**
* Show selected fragment and hide other.
*
* Could not use ft.hide/show for SupportMapFragment because this caused
* big delays coming back to main screen from other activities when the SupportMapFragment was
* in its hidden state. It also caused the UI to become unresponsive.
*
* I solved this by hiding/showing the SupportMapFragment by removing/adding the fragment for
* its container view. Working on 2.3.3 and Honeycomb --> KitKat emulators
*/
private void showFragment(Fragment fragmentIn) {
if (fragmentIn == null || mFragmentVisible == fragmentIn) {
return;
}
View mapView=mMapFragment.getView();
FragmentTransaction ft = getSupportFragmentManager().beginTransaction();
if(fragmentIn instanceof map_fragment){
//show map
if (mapView.getParent()!=mFragmentContainer) { //mFragmentContainer is FrameLayout
mFragmentContainer.addView(mapView);
}
ft.hide(mPlaceListFragment);
}else{
//show list
mFragmentContainer.removeView(mapView);
ft.show(mPlaceListFragment);
}
ft.commit();
mFragmentVisible = fragmentIn;
}