Methods Summary |
---|
public abstract void | destroyLoader(int id)Stops and removes the loader with the given ID. If this loader
had previously reported data to the client through
{@link LoaderCallbacks#onLoadFinished(Loader, Object)}, a call
will be made to {@link LoaderCallbacks#onLoaderReset(Loader)}.
|
public abstract void | dump(java.lang.String prefix, java.io.FileDescriptor fd, java.io.PrintWriter writer, java.lang.String[] args)Print the LoaderManager's state into the given stream.
|
public static void | enableDebugLogging(boolean enabled)Control whether the framework's internal loader manager debugging
logs are turned on. If enabled, you will see output in logcat as
the framework performs loader operations.
LoaderManagerImpl.DEBUG = enabled;
|
public abstract android.support.v4.content.Loader | getLoader(int id)Return the Loader with the given id or null if no matching Loader
is found.
|
public boolean | hasRunningLoaders()Returns true if any loaders managed are currently running and have not
returned data to the application yet. return false;
|
public abstract android.support.v4.content.Loader | initLoader(int id, android.os.Bundle args, android.support.v4.app.LoaderManager$LoaderCallbacks callback)Ensures a loader is initialized and active. If the loader doesn't
already exist, one is created and (if the activity/fragment is currently
started) starts the loader. Otherwise the last created
loader is re-used.
In either case, the given callback is associated with the loader, and
will be called as the loader state changes. If at the point of call
the caller is in its started state, and the requested loader
already exists and has generated its data, then
callback {@link LoaderCallbacks#onLoadFinished} will
be called immediately (inside of this function), so you must be prepared
for this to happen.
|
public abstract android.support.v4.content.Loader | restartLoader(int id, android.os.Bundle args, android.support.v4.app.LoaderManager$LoaderCallbacks callback)Starts a new or restarts an existing {@link android.content.Loader} in
this manager, registers the callbacks to it,
and (if the activity/fragment is currently started) starts loading it.
If a loader with the same id has previously been
started it will automatically be destroyed when the new loader completes
its work. The callback will be delivered before the old loader
is destroyed.
|