| /frameworks/base/core/java/android/app/ |
| UiModeManager.java | 52 * <p>You do not instantiate this class directly; instead, retrieve it through
|
| /frameworks/base/core/java/android/preference/ |
| PreferenceScreen.java | 41 * points to an instance of this class to show the preferences. To instantiate
|
| /frameworks/base/core/java/com/android/internal/app/procstats/ |
| DumpUtils.java | 85 * No instantiate
|
| /frameworks/base/docs/html/guide/topics/ui/controls/ |
| button.jd | 117 might be necessary if you instantiate the {@link android.widget.Button} at runtime or you need to
|
| /frameworks/base/docs/html/training/notify-user/ |
| navigation.jd | 199 // Instantiate a Builder object.
|
| /frameworks/base/docs/html/training/sync-adapters/ |
| creating-authenticator.jd | 145 access the authenticator, you can also use the service to instantiate the authenticator,
|
| /frameworks/base/docs/html/training/testing/integration-testing/ |
| content-provider-testing.jd | 135 Test with resolver methods: Even though you can instantiate a provider object in
|
| /frameworks/base/media/java/android/media/audiofx/ |
| BassBoost.java | 28 * <p>An application creates a BassBoost object to instantiate and control a bass boost engine in
|
| /frameworks/base/packages/DocumentsUI/tests/src/com/android/documentsui/dirlist/ |
| ModelTest.java | 99 // Instantiate the model with a dummy view adapter and listener that (for now) do nothing.
|
| /frameworks/base/services/core/java/com/android/server/pm/ |
| ShortcutParser.java | 125 // We instantiate ShortcutInfo at <shortcut>, but we add it to the list at </shortcut>,
|
| /frameworks/base/tools/layoutlib/bridge/src/android/view/ |
| BridgeInflater.java | 88 * Instantiate a new BridgeInflater with an {@link LayoutlibCallback} object.
|
| /frameworks/native/include/android/ |
| native_activity.h | 239 * This is the function that must be in the native code to instantiate the
|
| /frameworks/support/compat/java/android/support/v4/view/ |
| ActionProvider.java | 78 * from the constructor to instantiate a {@link android.view.LayoutInflater} and
|
| /frameworks/support/core-ui/java/android/support/v4/view/ |
| NestedScrollingChildHelper.java | 27 * <p>{@link android.view.View View} subclasses should instantiate a final instance of this
|
| /frameworks/support/fragment/java/android/support/v4/app/ |
| FragmentTabHost.java | 348 newTab.fragment = Fragment.instantiate(mContext,
|
| /frameworks/support/v13/java/android/support/v13/app/ |
| FragmentTabHost.java | 341 newTab.fragment = Fragment.instantiate(mContext,
|
| /hardware/invensense/6515/libsensors_iio/software/core/driver/include/ |
| mlsl.h | 63 * inv_serial_start() is mandatory to instantiate the communication
|
| /hardware/invensense/65xx/libsensors_iio/software/core/driver/include/ |
| mlsl.h | 63 * inv_serial_start() is mandatory to instantiate the communication
|
| /libcore/jsr166-tests/src/test/java/jsr166/ |
| BlockingQueueTest.java | 34 * implementation class, most importantly how to instantiate
|
| /libcore/libart/src/main/java/java/lang/ |
| CaseMapper.java | 36 * this class should be changed so that you instantiate it with the String and its value,
|
| /libcore/luni/src/main/java/javax/xml/xpath/ |
| XPathFactoryFinder.java | 258 debugPrintln("failed to instantiate "+className);
|
| /libcore/luni/src/main/java/org/w3c/dom/ |
| Document.java | 40 * implementations may instantiate different types of
71 * @param tagName The name of the element type to instantiate. For XML,
323 * instantiate.
388 * instantiate.
[all...] |
| /libcore/luni/src/main/java/org/xml/sax/ |
| DocumentHandler.java | 32 * the default functionality; parser writers can instantiate
|
| HandlerBase.java | 27 * instantiate this class to provide default handlers when the
|
| /libcore/ojluni/src/main/java/java/net/ |
| package.html | 85 As mentioned, URL and URLConnection rely on protocol handlers which must be present, otherwise an Exception is thrown. This is the major difference with URIs which only identify resources, and therefore don't need to have access to the protocol handler. So, while it is possible to create an URI with any kind of protocol scheme (e.g. <code>myproto://myhost.mydomain/resource/</code>), a similar URL will try to instantiate the handler for the specified protocol; if it doesn't exist an exception will be thrown.</p>
|
