java.lang.Object | |
↳ | android.support.v4.content.ContextCompat |
Known Direct Subclasses |
Helper for accessing features in Context
introduced after API level 4 in a backwards compatible fashion.
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Return a drawable object associated with a particular resource ID.
| |||||||||||
Returns absolute paths to application-specific directories on all
external storage devices where the application can place cache files it
owns.
| |||||||||||
Returns absolute paths to application-specific directories on all
external storage devices where the application can place persistent files
it owns.
| |||||||||||
Returns absolute paths to application-specific directories on all
external storage devices where the application's OBB files (if there are
any) can be found.
| |||||||||||
Start a set of activities as a synthesized task stack, if able.
| |||||||||||
Start a set of activities as a synthesized task stack, if able.
|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
|
Return a drawable object associated with a particular resource ID.
Starting in L
, the returned
drawable will be styled for the specified Context's theme.
id | The desired resource identifier, as generated by the aapt tool. This integer encodes the package, type, and resource entry. The value 0 is an invalid identifier. |
---|
Returns absolute paths to application-specific directories on all external storage devices where the application can place cache files it owns. These files are internal to the application, and not typically visible to the user as media.
This is like getCacheDir()
in that these files will be
deleted when the application is uninstalled, however there are some
important differences:
External storage devices returned here are considered a permanent part of the device, including both emulated external storage and physical media slots, such as SD cards in a battery compartment. The returned paths do not include transient devices, such as USB flash drives.
An application may store data on any or all of the returned devices. For
example, an app may choose to store large files on the device with the
most available space, as measured by StatFs
.
Starting in KITKAT
, no permissions
are required to write to the returned paths; they're always accessible to
the calling app. Before then,
WRITE_EXTERNAL_STORAGE
is required to
write. Write access outside of these paths on secondary external storage
devices is not available. To request external storage access in a
backwards compatible way, consider using android:maxSdkVersion
like this:
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="18" />
The first path returned is the same as
getExternalCacheDir()
. Returned paths may be null
if a storage device is unavailable.
Returns absolute paths to application-specific directories on all external storage devices where the application can place persistent files it owns. These files are internal to the application, and not typically visible to the user as media.
This is like getFilesDir()
in that these files will be
deleted when the application is uninstalled, however there are some
important differences:
External storage devices returned here are considered a permanent part of the device, including both emulated external storage and physical media slots, such as SD cards in a battery compartment. The returned paths do not include transient devices, such as USB flash drives.
An application may store data on any or all of the returned devices. For
example, an app may choose to store large files on the device with the
most available space, as measured by StatFs
.
Starting in KITKAT
, no permissions
are required to write to the returned paths; they're always accessible to
the calling app. Before then,
WRITE_EXTERNAL_STORAGE
is required to
write. Write access outside of these paths on secondary external storage
devices is not available. To request external storage access in a
backwards compatible way, consider using android:maxSdkVersion
like this:
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="18" />
The first path returned is the same as
getExternalFilesDir(String)
. Returned paths may be
null
if a storage device is unavailable.
Returns absolute paths to application-specific directories on all external storage devices where the application's OBB files (if there are any) can be found. Note if the application does not have any OBB files, these directories may not exist.
This is like getFilesDir()
in that these files will be
deleted when the application is uninstalled, however there are some
important differences:
External storage devices returned here are considered a permanent part of the device, including both emulated external storage and physical media slots, such as SD cards in a battery compartment. The returned paths do not include transient devices, such as USB flash drives.
An application may store data on any or all of the returned devices. For
example, an app may choose to store large files on the device with the
most available space, as measured by StatFs
.
Starting in KITKAT
, no permissions
are required to write to the returned paths; they're always accessible to
the calling app. Before then,
WRITE_EXTERNAL_STORAGE
is required to
write. Write access outside of these paths on secondary external storage
devices is not available. To request external storage access in a
backwards compatible way, consider using android:maxSdkVersion
like this:
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" android:maxSdkVersion="18" />
The first path returned is the same as getObbDir()
.
Returned paths may be null
if a storage device is unavailable.
Start a set of activities as a synthesized task stack, if able.
In API level 11 (Android 3.0/Honeycomb) the recommended conventions for app navigation using the back key changed. The back key's behavior is local to the current task and does not capture navigation across different tasks. Navigating across tasks and easily reaching the previous task is accomplished through the "recents" UI, accessible through the software-provided Recents key on the navigation or system bar. On devices with the older hardware button configuration the recents UI can be accessed with a long press on the Home key.
When crossing from one task stack to another post-Android 3.0, the application should synthesize a back stack/history for the new task so that the user may navigate out of the new task and back to the Launcher by repeated presses of the back key. Back key presses should not navigate across task stacks.
startActivities provides a mechanism for constructing a synthetic task stack of multiple activities. If the underlying API is not available on the system this method will return false.
context | Start activities using this activity as the starting context |
---|---|
intents | Array of intents defining the activities that will be started. The element length-1 will correspond to the top activity on the resulting task stack. |
Start a set of activities as a synthesized task stack, if able.
In API level 11 (Android 3.0/Honeycomb) the recommended conventions for app navigation using the back key changed. The back key's behavior is local to the current task and does not capture navigation across different tasks. Navigating across tasks and easily reaching the previous task is accomplished through the "recents" UI, accessible through the software-provided Recents key on the navigation or system bar. On devices with the older hardware button configuration the recents UI can be accessed with a long press on the Home key.
When crossing from one task stack to another post-Android 3.0, the application should synthesize a back stack/history for the new task so that the user may navigate out of the new task and back to the Launcher by repeated presses of the back key. Back key presses should not navigate across task stacks.
startActivities provides a mechanism for constructing a synthetic task stack of multiple activities. If the underlying API is not available on the system this method will return false.
context | Start activities using this activity as the starting context |
---|---|
intents | Array of intents defining the activities that will be started. The element length-1 will correspond to the top activity on the resulting task stack. |
options | Additional options for how the Activity should be started. See {@link android.content.Context#startActivity(Intent, Bundle) |