本文介绍了哪里是getChildFragmentManager支持库V13?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Android的支持库V13应该从安卓3.1提供了新的API的支持。但是,据我可以告诉有儿童片段的支持。具体而言,在哪里getChildFragmentManager()?在V13支持库依赖于原生片段,其中没有添加这个方法,直到API级别17.我有一个最小的SDK 14级的应用程序,所以我应该能够使用V13支持库,但似乎我不能。

我不希望所有的方式回到V4支持库,并采取所有它的重量。在V13库是完美的,否则。

解决方案

不是真的。

正确的。你无法从Java中的外部库改变现有的类。 android.app.Fragment 已经存在,因此磁带库无法添加方法片段

您可以简单地不能使用嵌套的片段。或者,使用片段的backport。

Android的支持 - v13.jar Android的支持 - v4.jar 大。

它增加了一些课程,如原生片段实施 FragmentPagerAdapter FragmentStatePagerAdapter ,这是不需要的应用程序谁没有原生的碎片,因为它们的机器人:的minSdkVersion 低于11

Android的支持 - v13.jar 包含所有的 android.support.v4 和所有 android.support.v13 类的SDK。

Android support library v13 is supposed to provide support for newer APIs from Android 3.1. However, as far as I can tell there is no support for child fragments. Specifically, where is getChildFragmentManager()? The v13 support library relies on native fragments, which didn't add this method until API level 17. I have an app with minimum SDK level 14 so I should be able to use the v13 support library, but it seems I can't.

I don't want to go all the way back to the v4 support library and take on all it's weight. The v13 library is perfect otherwise.

解决方案

Not really.

Correct. You cannot change existing classes from an external library in Java. android.app.Fragment already exists, therefore the library cannot add methods to Fragment.

You can simply not use nested fragments. Or, use the fragments backport.

android-support-v13.jar is larger than android-support-v4.jar.

It adds some classes, like native-fragment implementations of FragmentPagerAdapter and FragmentStatePagerAdapter, that are not needed for apps who do not have native fragments, because their android:minSdkVersion is below 11.

android-support-v13.jar contains all of the android.support.v4 and all of the android.support.v13 classes from the SDK.

这篇关于哪里是getChildFragmentManager支持库V13?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-13 23:43