blocks|key|191853|text|对于导航菜单片断事务，我使用以下方法，这样片断将被添加并放在顶部。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|191854|String+name+=+"myFragment";
getSupportFragmentManager()
.beginTransaction()
.replace(R.id.content_frame,+fragment,+name)
.commit();|code-block|syntax|javascript|191855|查找attach()函数。它遵循不同的片段生命周期。还要确保你的布局文件framelayout是可见的。|191856|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For navigation menu fragment transactions I use the following approach, this way the fragment will be added and placed on top.

<pre><code>String name = "myFragment";
getSupportFragmentManager()
.beginTransaction()
.replace(R.id.content_frame, fragment, name)
.commit();
</code></pre>

Look up the attach() function. It follows a different fragment lifecycle.
Also make sure that your layout files framelayout is visible.

blocks|key|191879|text|如下所示修改您的代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|191880|if(fragment+!=+null)+{
++++++++//+attach+added+to+handle+viewpager+fragments
++++++++FragmentTransaction+trans+=+getSupportFragmentManager().beginTransaction();
++++++++trans.replace(R.id.content_frame,+fragment);
++++++++trans.addToBackStack(null);
++++++++trans.commit();
++++}+else+{
++++++++Log.d("Drawer+Activity","Error+in+creating+Fragment");
++++}|code-block|syntax|javascript|191881|如果解决方案对您不起作用，那么可以将xml代码与您的片段代码一起共享。|191882|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Modify your code as below:

<pre><code>if(fragment != null) {
 // attach added to handle viewpager fragments
 FragmentTransaction trans = getSupportFragmentManager().beginTransaction();
 trans.replace(R.id.content_frame, fragment);
 trans.addToBackStack(null);
 trans.commit();
 } else {
 Log.d("Drawer Activity","Error in creating Fragment");
 }
</code></pre>

If the solution doesn't work for you, share the xml code along with your fragment code.

blocks|key|191913|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|191914|添加片段后，它将被添加到activity状态，其视图将被添加到defined+Container视图。但是通过附加，如果片段还没有添加到UI中，则不会显示任何内容。它只是附加到片段管理器。然而，如果视图已经被添加到UI中的容器中，并在那之后被分离，那么通过附加它，它将再次显示在它的容器中。最后，如果您想临时销毁fragment+View，并希望在将来显示和构建它的视图而不丢失它在activity中的状态，您可以使用attach和detach。|blockquote|191915|191916|191917|https://stackoverflow.com/a/18979024/3329488|offset|length|191918|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|18|0|0^^$0|@$1|2|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|R|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|S|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|T|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|U|7|@]|8|@$H|V|I|W|1|X]]|9|$]]|$1|J|3|-4|4|5|6|Y|7|@]|8|@]|9|$]]]|K|$L|$4|M|N|O|9|$P|G]]]]

<blockquote>
 After adding Fragment it will be added to activity state and its view
 will be added to defined Container view. But by attaching nothing will
 be displayed if fragment was not already added to UI. It just attaches
 to fragment manager. However if view was already added to a container
 in UI and detached after that, by attaching it will be displayed again
 in its container. Finally you can use attach and detach if you want to
 destroy fragment View temporarily and want to display and build its
 view on future without losing its state inside activity.
</blockquote>

<a href="https://stackoverflow.com/a/18979024/3329488">https://stackoverflow.com/a/18979024/3329488</a>

blocks|key|3972630|text|我的解决方案是在替换片段时用唯一的标签标记所有的片段。在创建时，请确保您还为默认片段分配了一个唯一的标签。一种更有效的方法是在重新创建相同的片段之前识别该片段。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3972631|public+void+selectNavActivty(int+position){
//+TODO+Changing+between+the+different+screens+selection

++++FragmentManager+fragmentManager+=+getSupportFragmentManager();
++++fragment+=+fragmentManager.findFragmentById(R.id.content_frame);
++++String+fragmentTag+=+null;
++++switch+(position)+{
++++++++case+0:
++++++++++++fragmentTag+=+"case0Tag";+//+please+change+to+better+tag+name
++++++++++++break;
++++++++case+1:+
++++++++++++fragmentTag+=+"case1Tag";+//+please+change+to+better+tag+name
++++++++++++break;
++++++++default:
++++++++++++Log.d("Drawer+Activity","Error+in+creating+Fragment");
++++++++++++return;
++++}
++++if+(fragmentTag+!=+null+&&+!fragment.getTag().equals(fragmentTag))
++++fragmentManager.beginTransaction().replace(R.id.content_fragment,+fragment,+tag).commit();
}|code-block|syntax|javascript|3972632|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

My solution is to tag all the fragment with unique tag on fragment replacement. Make sure you also assign a unique tag to the default fragment during it creation. A more efficient way is to identify the fragment before you recreate the same one.

<pre><code>public void selectNavActivty(int position){
// TODO Changing between the different screens selection

 FragmentManager fragmentManager = getSupportFragmentManager();
 fragment = fragmentManager.findFragmentById(R.id.content_frame);
 String fragmentTag = null;
 switch (position) {
 case 0:
 fragmentTag = "case0Tag"; // please change to better tag name
 break;
 case 1: 
 fragmentTag = "case1Tag"; // please change to better tag name
 break;
 default:
 Log.d("Drawer Activity","Error in creating Fragment");
 return;
 }
 if (fragmentTag != null &amp;&amp; !fragment.getTag().equals(fragmentTag))
 fragmentManager.beginTransaction().replace(R.id.content_fragment, fragment, tag).commit();
}
</code></pre>

blocks|key|191975|text|在我的例子中，在旋转设备之后，显示了一个空白片段。我知道，在Activity.onCreate()中，我总是要求创建一个空白的Fragment，然后再创建一个需要的and。所以我把它的行为改为这样：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|191976|override+fun+onCreate(savedInstanceState:+Bundle?)+{
++++super.onCreate(savedInstanceState)

++++if+(savedInstanceState+==+null)+{
++++++++openEmptyFragment()
++++++++openAnotherFragment()
++++}
}|code-block|syntax|javascript|191977|我建议在添加新片段之前检查savedInstanceState+!=+null，就像用Why+won't+Fragment+retain+state+when+screen+is+rotated?编写的一样。|191978|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/14184182/why-wont-fragment-retain-state-when-screen-is-rotated^0|U|J|1R|8|0|0|D|Q|17|1J|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|M|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

In my case after rotating a device a blank fragment was shown. I understood that in an <code>Activity.onCreate()</code> I always called creating a blank <code>Fragment</code> and after that a needed one. So I changed it's behaviour to this:

<pre><code>override fun onCreate(savedInstanceState: Bundle?) {
 super.onCreate(savedInstanceState)

 if (savedInstanceState == null) {
 openEmptyFragment()
 openAnotherFragment()
 }
}
</code></pre>

I recommend to check <code>savedInstanceState != null</code> before adding new fragments, as written in <a href="https://stackoverflow.com/questions/14184182/why-wont-fragment-retain-state-when-screen-is-rotated">Why won&#39;t Fragment retain state when screen is rotated?</a>.

I am building a navigation drawer as designed by the google documentation however I have an issue where the fragment is not being replaced. <a href="http://developer.android.com/training/implementing-navigation/nav-drawer.html">http://developer.android.com/training/implementing-navigation/nav-drawer.html</a>

When the app first loads, the default fragment is loaded.
Clicking on another item on the drawer list leaves an empty view
However on rotating the device, loads the fragment chosen.

<pre><code>public void selectNavActivty(int position){
 // TODO Changing between the different screens selection
 fragment = null;
 switch (position) {
 case 0:
 fragment = OverLay.newInstance();
 break;
 case 1: 
 fragment = Dummy.newInstance();
 break;
 }

 if(fragment != null) {
 // attach added to handle viewpager fragments
 FragmentTransaction trans = getSupportFragmentManager().beginTransaction();
 trans.replace(R.id.content_frame, fragment).attach(fragment)
 .addToBackStack(null);

 trans.commit();
 getFragmentManager().executePendingTransactions();
 } else {
 Log.d("Drawer Activity","Error in creating Fragment");
 }
}
</code></pre>

Fragment Transaction load empty view but fragment is shown after rotating device

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在构建一个由google文档设计的导航抽屉，但是我有一个问题，片段没有被替换。当应用程序第一次加载时，会加载默认片段。点击抽屉列表上的另一项会留下一个空视图，但是在旋转设备时，会加载所选的片段。public void selectNavActivty(int position){    // TODO Changi...

问碎片事务加载空视图，但在旋转设备后显示碎片
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问碎片事务加载空视图，但在旋转设备后显示碎片EN