summaryrefslogtreecommitdiff
path: root/core/java/android/content/Loader.java
Commit message (Collapse)AuthorAgeFilesLines
* Migrate frameworks/base javadocs references to androidxAlan Viverette2022-02-091-4/+4
| | | | | | | | | | | Does not remove Support Library artifacts from docs classpath (ApiDocs.bp) because they are still used in development/samples, which is not as easy to migrate as javadoc. Bug: 158779503 Test: make docs Exempt-From-Owner-Approval: Mass find/replace for androidx migration Change-Id: Icf7f53ec36a0e970413352e2ebf40ce9d60ed17e
* Improve Fragment+Loader deprecation JavadocIan Lake2017-12-201-2/+3
| | | | | | | | | | | | | | | Make it clear that the framework versions of Fragments and Loaders should be replaced with their identically named versions in the Support Library. Reference the recent work on Lifecycle as an example of a Support Library only change that should motivate developers to switch to the Support Library equivalents. Test: Reviewed new Javadoc BUG: 70336450 Change-Id: I93151fa0a316bba824c2e55f80f7de9d30bed3c6
* Deprecate framework Fragments and LoadersIan Lake2017-11-131-0/+12
| | | | | | | | | | | | Redirect developers to use the Support Library versions of Fragments and Loaders to ensure that they get consistent behavior across versions of Android and all devices as well as access to Lifecycle improvements. Test: Confirmed APIs deprecated in current.txt BUG: 68381801 Change-Id: I58ec599e557fc93c8547c45ba7c9ced96b0c8616
* docs: fix link in Loader reference pageMark Lu2016-08-121-1/+1
| | | | | Bug: 29764129 Change-Id: I5ca881bb30adbbaf65ba37b1cf63903a4fc5600e
* Don't lose content change during rollback for loader already startedAdam Powell2016-04-271-1/+1
| | | | | | | | | | | | | | Framework edition If a loader is already started when we try to rollback a content change, force a new load instead of simply setting the flag to refresh next time. Bug 28406183 https://code.google.com/p/android/issues/detail?id=208278 Change-Id: If11d79088d30dd2dc48cf1b3d2882f3712b6cddb
* am 0047d3e0: am e253b514: am 29d60b95: am 8d41e653: Merge "Miscellaneous ↵Elliott Hughes2014-02-211-1/+1
|\ | | | | | | | | | | | | small documentation fixes." * commit '0047d3e025b43fd2dc05734f7ea6229291445046': Miscellaneous small documentation fixes.
| * Miscellaneous small documentation fixes.Mark Doliner2014-01-031-1/+1
| | | | | | | | | | | | Most of these I noticed on my own. The change to docs/html/tools/testing/testing_ui.jd is mentioned in a bug report: https://code.google.com/p/android/issues/detail?id=56324 Signed-off-by: Mark Doliner <markdoliner@google.com>
* | Minor code cleanup in loaders.Jeff Brown2013-10-091-1/+1
|/ | | | Change-Id: I38147eb9e494b53d41ca3cad042d804631916941
* Fix a bug where we could lose a loader content change.Dianne Hackborn2013-03-141-5/+37
| | | | | | | | | | | | | | | | | If AsyncTaskLoader starts a background update due to a content change, and that update is cancelled, we drop the data when it finally arrives and forget that the content changed. If we later come back to the loader, we then end up showing stale data because we don't know that we still need to update due to the old content change. This change adds a couple new APIs to Loader to deal with the time between when you ask for whether there is a content change and finally either commit the data or cancel the update. AsyncTaskLoader is changed to make use of this so that it doesn't lose changes. Change-Id: I3866236b1c22bb9138f2d9f6032b126aeaee2e6e
* Support automatic cancellation of Loaders.Jeff Brown2012-02-011-0/+101
| | | | Change-Id: I18d3f49e413f48fcdd519d15e99c238ad54d35b9
* SDK only: now that support lib is in SDK, we can link to it.Dianne Hackborn2011-12-121-0/+15
| | | | | | | | | | | Update some of the platform documentation to directly link to relevent support lib docs. Yay! Also improve BroadcastReceiver documentation to more clearly discussion security around receivers, and how the support lib's LocalBroadcastManager can help. Change-Id: I563c7516d5fbf91ab884c86bc411aff726249e42
* Various performance and other work.Dianne Hackborn2011-10-311-1/+25
| | | | | | | | | | | | | | | | | | - IME service now switches between visible and perceptible depending on whether it is being showm, allowing us to more aggressively free its memory when not shown. - The activity display time is no longer delayed by the activity transition animation. - New -R (repeat) option for launching activities with the am command. - Improved some documentation on Loader to be clear about some methods that apps should not normally call. - FrameworkPerf test now allows you to select individual tests to run. Change-Id: Id1f73de66dc93d63212183958a72119ad174318b
* docs: add developer guide cross-references, Project ACREJoe Fernandez2011-10-041-2/+6
| | | | Change-Id: I5df1c4e13af67ff4c4a5b22f3cb1247bf0103b09
* cherrypick Change-Id: I4713d3977a0a1514ff9c4217e7f3723c0346d0d8Scott Main2011-07-271-0/+2
| | | | | | docs: revise ActionBar class summary and add a few links to dev guide docs Change-Id: I14df84b16d7bdab85aa74d8b8211e988b0519115
* Deprecate a bunch of APIs.Dianne Hackborn2011-04-201-4/+11
| | | | | | And clean up some documentation. Change-Id: I7882183b3daf883b7ac6098d19f88dc7cfbcdf61
* Fix issue #3381489: IllegalStateException: attempt to re-open...Dianne Hackborn2011-01-301-0/+35
| | | | | | | | | | | | | | | | | | | ...an already-closed object: android.database.sqlite.SQLiteQuery It turns out there is a state we are missing -- the loader is still needed, but in the inactive list. In this case the loader needs to continue holding on to its current data, and not deliver any new data (which would result in it releasing its old data). This introduces the new state to Loader, and uses it in AsyncTaskLoader so all subclasses of that should get the new correct behavior. A further improvement would be to unregister CursorLoader's content listener when going in to this state, but that can wait for later. Change-Id: I6d30173b94f8e30b5be31d018accd328cc3388ec
* Implement issue # 3255887 could CursorLoader offer...Dianne Hackborn2011-01-081-18/+33
| | | | | | | | | | | | | | | | | | ...to throttle contentobserver-based requeries Why yes, I guess it could. This also reworks AsyncTaskLoader to not generate multiple concurrent tasks if it is getting change notifications before the last background task is complete. And removes some of the old APIs that had been deprecated but need to be gone for final release. And fixes a few little problems with applying the wrong theme in system code. Change-Id: Ic7a665b666d0fb9d348e5f23595532191065884f
* Fix issue #3301572: onCreateLoader must not be a member class: ↵Dianne Hackborn2010-12-211-9/+38
| | | | | | | | VolumeMetadataLoader Also some various cleanup. Change-Id: I8e8616a86c50c86817f7ec9bb02a5954c1ccd84f
* More cleanup of Loader APIs.Dianne Hackborn2010-12-201-13/+125
| | | | | | | | - Remove old method names. - Introduce onXxx() hooks to Loader. - Improve debugging. Change-Id: I3fba072a05c7023aa7d2c3eb4e126feb514ab6d8
* Fix issue #3272082: Contacts: when going back from edit view,Dianne Hackborn2010-12-161-6/+18
| | | | | | | | | | | | | | | | | | | | | list UI is not ready yet This involves some reworking of Loaders. Loaders, in particular CursorLoader, are now expected to retain their current data after being stopped. This allows applications to keep that data across onStop() -> onStart(), so when the user returns to the app it doesn't have to wait for the data to reload and thus cause flicker. This includes various API changes to better reflect the new semantics, plus a new LoaderCallbacks method to tell the application when it is actually time to stop their use of a loader's data. Note this is somewhat half-done, to help checking in the extensive application changes that are required without causing build breakage. Change-Id: Ib4b3bf8185a6da46e7f06ca125521d65e2e380a1
* Adding a method called when detecting content change.Makoto Onuki2010-08-031-4/+14
| | | | | | | | | | | | | | Added Loader.onContentChanged() which is called by ForceLoadContentObserver when it detects a change, rather than forceLoad(). By default onContentChanged() just calls forceLoad(), so there's no change in behavior. This is useful when a subclass wants to perform custom operations upon data chantes. For example, a subclass may want to limit the number of automatic requeries per second. Change-Id: I493dac3f4f1a75b056d2c7065336ea9252dbf424
* Add the Loader and supporting classes.Jeff Hamilton2010-05-181-0/+154
Loaders are designed to make it easier to manage asynchronously loading data. Change-Id: I948db08c721411e94fca071dc6fb4db2b83ea4d6
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-21 04:59:47 +0000