blocks|key|2729193|text|它们非常相似。查看MenuInflator的源代码，它使用上下文的唯一目的是访问资源文件。因此，特定的上下文对MenuInflator来说并不重要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2729194|至于内存泄漏，您参考的文章中说|2729195|2729196|避免内存泄漏的最明显的方法是避免在它自己的作用域之外转义上下文|blockquote|2729197|2729198|2729199|除非您将MenuInflator+(或菜单)传递给另一个类，否则它将包含在活动中，不会泄漏。|2729200|编辑|offset|length|style|BOLD|2729201|此外，对于new+MenuInflator()来说，Activity.getMenuInflator()只是一种方便的方法。实际上，这是Activity类中的方法：|CODE|2729202|public+MenuInflater+getMenuInflater()+{
++++return+new+MenuInflater(this);
}|code-block|syntax|javascript|2729203|使用方便的方法通常更好，因为它们允许在未来的版本中更改底层实现，而不必更改代码。例如，如果将上述方法修改为返回一个缓存实例，而不是每次都创建一个新实例。|2729204|entityMap^0|0|0|0|0|0|0|0|0|2|0|5|I|Q|Q|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|16|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@$N|1B|O|1C|P|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1D|8|@$N|1E|O|1F|P|T]|$N|1G|O|1H|P|T]]|9|@]|A|$]]|$1|U|3|V|5|W|7|1I|8|@]|9|@]|A|$X|Y]]|$1|Z|3|10|5|6|7|1J|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|12|$]]

They are very similar. Looking through the MenuInflator's source, the only thing it uses the context for is to access the resource files. So the specific context doesn't matter to the MenuInflator.

As for memory leaks, the article you reference says 

<blockquote>
 The most obvious [way to avoid memory leaks] is to avoid escaping the
 context outside of its own scope
</blockquote>

Unless you pass the MenuInflator (or Menu) to another class then it is contained in the activity and won't be leaked.

EDIT

In addition <code>Activity.getMenuInflator()</code> is just a convenience method for <code>new MenuInflator()</code>. In fact this is the method inside the Activity class:

<pre><code>public MenuInflater getMenuInflater() {
 return new MenuInflater(this);
}
</code></pre>

It is usually better to use convenience methods since they allow for the underlying implementation to change in future versions without you having to change your code. For example if the above method is modified to return a cached instance instead of creating a new one each time.

blocks|key|1960792|text|您应该使用传递给public+void+onCreateOptionsMenu(Menu+menu,+MenuInflater+inflater)方法的MenuInflater实例(请注意第二个参数)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1960793|这没有真正的区别，因为通常你一使用完它就会“忘记”它，但是如果你已经从参数中创建了一个，为什么还要创建一个呢？|1960794|entityMap^0|8|1T|24|C|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

You should use <code>MenuInflater</code> instance that is passed to the method <code>public void onCreateOptionsMenu(Menu menu, MenuInflater inflater)</code> (notice the 2nd argument) 
There's no real difference, because normally you will "forget" it as soon as you finish using it, but why would you need to create one if you already have one from the arguments?

blocks|key|5046767|text|从以下内容更改：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5046768|MenuInflater+inflater+=+getMenuInflater();|code-block|syntax|javascript|5046769|要这样做：|5046770|MenuInflater+inflater+=+getActivity().getMenuInflater();|5046771|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Change from this :

<pre><code>MenuInflater inflater = getMenuInflater();
</code></pre>

To this:

<pre><code>MenuInflater inflater = getActivity().getMenuInflater();
</code></pre>

I'm creating new option menu inside fragment but after reading 
<a href="http://developer.android.com/resources/articles/avoiding-memory-leaks.html" rel="noreferrer">http://developer.android.com/resources/articles/avoiding-memory-leaks.html</a>
which said to it's better to use context-application than context-activity, I'm afraid to use getActivity().getMenuInflater() 

So, actually which one better

<pre><code>@Override
public void onCreateOptionsMenu(Menu menu, MenuInflater inflater) {
 MenuInflater mInflater = new MenuInflater(getActivity().getApplicationContext());
 mInflater.inflate(R.menu.simple_menu, menu);
}
</code></pre>

Or the one call activity

<pre><code>@Override
public void onCreateOptionsMenu(Menu menu, MenuInflater inflater) {
 MenuInflater mInflater = getActivity().getMenuInflater();
 mInflater.inflate(R.menu.simple_menu, menu);

}
</code></pre>

and, what's the differences between the two of 'em? or..both are just the same?

Thanks.

create new menuInflater or getMenuInflater() from activity?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我在fragment中创建了新的选项菜单，但在阅读了之后，它告诉我使用上下文应用程序比使用上下文活动更好，我害怕使用getActivity().getMenuInflater()所以，实际上哪一个更好@Overridepublic void onCreateOptionsMenu(Menu menu, MenuInfl...

问是否从activity创建新的menuInflater或getMenuInflater()？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问是否从activity创建新的menuInflater或getMenuInflater()？EN