由网友(Cold mood（冷情绪）)分享简介：我一直在阅读有关从Android开发博客布局优化和我一直在使用hierarchyviewer，看看我能可能变平或合并的布局/元素。但这里是我一直看到在我看来，层次...... NoSaveStateFrameLayout东西。任何人都可以揭示出这个一些启示？它显示了（通常）一个LinearLayout中之前，它似乎很没...

我一直在阅读有关从Android开发博客布局优化和我一直在使用hierarchyviewer，看看我能可能变平或合并的布局/元素。但这里是我一直看到在我看来，层次...... NoSaveStateFrameLayout东西。任何人都可以揭示出这个一些启示？它显示了（通常）一个LinearLayout中之前，它似乎很没用，只是增加了一个（不必要的）级别的层次结构。我试图寻找这是什么，但我有没有运气。

I've been reading about layout optimization from the Android Dev blogs and I've been using hierarchyviewer to see where I can possibly flatten or merge layouts/elements. But here is something that I keep seeing in my view hierarchy...NoSaveStateFrameLayout. Can anyone shed some light on this? It shows up (usually) before a LinearLayout and it seems quite useless and just adds another (unnecessary) level to the hierarchy. I tried searching for what this is but I've had no luck.

推荐答案

这是支持库的片段实现的实现细节。这是它的注释：

It's an implementation detail of the support library's fragment implementation. This is the comment from it:

/**
 * Pre-Honeycomb versions of the platform don't have {@link View#setSaveFromParentEnabled(boolean)},
 * so instead we insert this between the view and its parent.
 */