LoaderManager.LoaderCallbacks
public
static
interface
LoaderManager.LoaderCallbacks
android.app.LoaderManager.LoaderCallbacks<D> |
This interface was deprecated
in API level 28.
Use the
Support Library LoaderManager.LoaderCallbacks
Callback interface for a client to interact with the manager.
Summary
Public methods | |
---|---|
abstract
Loader<D>
|
onCreateLoader(int id, Bundle args)
Instantiate and return a new Loader for the given ID. |
abstract
void
|
onLoadFinished(Loader<D> loader, D data)
Called when a previously created loader has finished its load. |
abstract
void
|
onLoaderReset(Loader<D> loader)
Called when a previously created loader is being reset, and thus making its data unavailable. |
Public methods
onCreateLoader
public abstract Loader<D> onCreateLoader (int id, Bundle args)
Instantiate and return a new Loader for the given ID.
Parameters | |
---|---|
id |
int : The ID whose loader is to be created. |
args |
Bundle : Any arguments supplied by the caller. |
Returns | |
---|---|
Loader<D> |
Return a new Loader instance that is ready to start loading. |
onLoadFinished
public abstract void onLoadFinished (Loader<D> loader, D data)
Called when a previously created loader has finished its load. Note
that normally an application is not allowed to commit fragment
transactions while in this call, since it can happen after an
activity's state is saved. See FragmentManager.openTransaction()
for further discussion on this.
This function is guaranteed to be called prior to the release of the last data that was supplied for this Loader. At this point you should remove all use of the old data (since it will be released soon), but should not do your own release of the data since its Loader owns it and will take care of that. The Loader will take care of management of its data so you don't have to. In particular:
-
The Loader will monitor for changes to the data, and report them to you through new calls here. You should not monitor the data yourself. For example, if the data is a
Cursor
and you place it in aCursorAdapter
, use theCursorAdapter.CursorAdapter(android.content.Context, android.database.Cursor, int)
constructor without passing in eitherCursorAdapter.FLAG_AUTO_REQUERY
orCursorAdapter.FLAG_REGISTER_CONTENT_OBSERVER
(that is, use 0 for the flags argument). This prevents the CursorAdapter from doing its own observing of the Cursor, which is not needed since when a change happens you will get a new Cursor throw another call here. - The Loader will release the data once it knows the application
is no longer using it. For example, if the data is
a
Cursor
from aCursorLoader
, you should not call close() on it yourself. If the Cursor is being placed in aCursorAdapter
, you should use theCursorAdapter.swapCursor(android.database.Cursor)
method so that the old Cursor is not closed.
Parameters | |
---|---|
loader |
Loader : The Loader that has finished. |
data |
D : The data generated by the Loader. |
onLoaderReset
public abstract void onLoaderReset (Loader<D> loader)
Called when a previously created loader is being reset, and thus making its data unavailable. The application should at this point remove any references it has to the Loader's data.
Parameters | |
---|---|
loader |
Loader : The Loader that is being reset. |