summaryrefslogtreecommitdiff
path: root/core/java/android/app/DialogFragment.java
Commit message (Collapse)AuthorAgeFilesLines
* Migrate frameworks/base javadocs references to androidxAlan Viverette2022-02-091-1/+1
| | | | | | | | | | | 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
* Add maxTargetSdk restriction to unused APIs.Mathew Inwood2020-10-291-2/+3
| | | | | | | | | | | | | | | | | | | These are APIs that have @UnsupportedAppUsage but for which we don't have any evidence of them currently being used, so should be safe to remove from the unsupported list. This is a resubmit of ag/12929664 with some APIs excluded that caused test failures; see bugs 171886397, 171888296, 171864568. APIs excluded: Landroid/bluetooth/le/ScanRecord;->parseFromBytes([B)Landroid/bluetooth/le/ScanRecord; Landroid/os/Process;->myPpid()I Landroid/os/SharedMemory;->getFd()I Landroid/hardware/input/InputManager;->INJECT_INPUT_EVENT_MODE_WAIT_FOR_FINISH:I Bug: 170729553 Test: Treehugger Change-Id: I8285daa8530260251ecad6f3f38f98e263629ca7
* Revert "Add maxTargetSdk restriction to unused APIs."Hongwei Wang2020-10-281-3/+2
| | | | | | | | | This reverts commit 72f07d6a8a32db4a0dedd7682a0b3385be2b9cd6. Reason for revert: Droidcop-triggered revert due to breakage https://android-build.googleplex.com/builds/quarterdeck?testMethod=testAppZygotePreload&testClass=android.app.cts.ServiceTest&atpConfigName=suite%2Ftest-mapping-presubmit-retry_cloud-tf&testModule=CtsAppTestCases&fkbb=6936597&lkbb=6936969&lkgb=6936551&testResults=true&branch=git_master&target=cf_x86_phone-userdebug>, bug b/171886397 Bug: 171886397 Change-Id: Ibe0f0430a3451477c1ee8ef56a596e91ea1e7672
* Add maxTargetSdk restriction to unused APIs.Mathew Inwood2020-10-271-2/+3
| | | | | | | | | | These are APIs that have @UnsupportedAppUsage but for which we don't have any evidence of them currently being used, so should be safe to remove from the unsupported list. Bug: 170729553 Test: Treehugger Change-Id: I4c8fd0006f950de9955242e93968fb0996ceb372
* Use new UnsupportedAppUsage annotation.Artur Satayev2019-12-181-1/+1
| | | | | | | | Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library. Bug: 145132366 Test: m && diff unsupportedappusage_index.csv Change-Id: I8789f8499d4dca08580672e9e45ed9a7026dd686
* Add @UnsupportedAppUsage annotationsMathew Inwood2018-08-141-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | For packages: android.app.usage android.app.trust android.app.timezonedetector android.app.timezone android.app.timedetector android.app.job android.app.backup android.app.assist android.app.admin android.app This is an automatically generated CL. See go/UnsupportedAppUsage for more details. Exempted-From-Owner-Approval: Mechanical changes to the codebase which have been approved by Android API council and announced on android-eng@ Bug: 110868826 Test: m Change-Id: I618c5dc4462ae990d9df45c3e9ed3f092cc5138c
* Improve Fragment+Loader deprecation JavadocIan Lake2017-12-201-1/+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/+3
| | | | | | | | | | | | 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
* Make public getFragments() and onGetLayoutInflater() methodsGeorge Mount2017-03-291-2/+2
| | | | | | Bug 34703669 Test: I846ef668e3dd7d664cfb56d2b9400467ba9b79f4 Change-Id: Ie202960ada86b25e964f98a639b5f5740c8fdb79
* Revert "Make public getFragments() and onGetLayoutInflater() methods"Jeff Tinker2017-03-291-2/+2
| | | | | | | | | This reverts commit 599be3d01ed1811ae365085e67a15d082170b583. This change is being reverted because it broke git_master build. Change-Id: I54ab9cd3d9e08dcf870f472fda08cc44e57986d0 bug: 34703669
* Make public getFragments() and onGetLayoutInflater() methodsGeorge Mount2017-03-281-2/+2
| | | | | | | Bug 34703669 Test: I71856306a7bb67aacb84be17165e7e095653c20a Change-Id: I41999d0f5e6d75afebbbf67ad5bf49fa0cca509e
* Remove dependencies on Activity from common Fragment superclassesAdam Powell2016-04-221-5/+8
| | | | | | | | Allow common Fragments to be used in non-Activity hosts. Bug 28337394 Change-Id: Id3baa3ef19ea41ff43ca76be89ced7530fbadfab
* Method to show DialogFragment allowing state loss.Jeff Sharkey2015-08-131-0/+9
| | | | | | | Same as show(), but allowing state loss. Bug: 22867250 Change-Id: Ib779d8a3febc70ad47a9c1a9099d858707bad733
* Remove dependency upon FragmentActivityTodd Kennedy2015-04-301-1/+1
| | | | | | | | | | The FragmentManagerImpl is intimately tied with a FragmentActivity. In many cases, we want to be able to create / manage Fragments outside of a FragmentManager. This defines a FragmentController interface that can be used by any class to host Fragments. Bug: 19569654 Change-Id: I6816a5c1815122d206062b9f4584ad460b3d41dd
* docs: misc bugs from external trackerScott Main2012-07-031-1/+1
| | | | Change-Id: I02d0d82c220401ac3a1ca180e8331a0f6dcd9e50
* Fix bug 5159736 - Make DeviceDefault the defaultAdam Powell2011-08-141-1/+1
| | | | | | | Have the framework refer to the DeviceDefault themes for ICS apps that don't explicitly request another theme. Change-Id: I27dd0bbaa60f71df4f36e47d260f556d923ba075
* Fix issues #4087362 and #4087356Dianne Hackborn2011-03-111-0/+10
| | | | | | | | | | | | | | 4087362: Provide a safer way to call DialogFragment.dismiss() 4087356: PreferenceActivity.invalidateHeaders() can cause IllegalStateException: Can not perform this action after onSaveInstanceState These are very safe; the first is just a new public API that allows you to use an existing feature in DialogFragment, and the second just uses the version of commit that avoids the failure if happening at a point where the operation would be lost if restored from the last state (which is no big deal for preferences). Change-Id: I53971c9fb1efdcd599694cdcd4585b81afc156b8
* Merge "Fix issue #3405957 com.android.settings: ↵Dianne Hackborn2011-03-011-9/+56
|\ | | | | | | java.lang.NullPointerException..."
| * Fix issue #3405957 com.android.settings: java.lang.NullPointerException...Dianne Hackborn2011-03-011-9/+56
| | | | | | | | | | | | | | | | ...at android.app.DialogFragment.dismissInternal(DialogFragment.java:264) Don't allow a DialogFragment to be dismissed twice. Change-Id: Id2e9e3be1046b0d7862492c57c36001d8fd44a69
* | Fix issue #3411615: Crash when getting dialog layout inflator.Dianne Hackborn2011-03-011-1/+5
|/ | | | | | | Well, I'm not sure it is right for onCreateDialog() to return a null dialog, but if it does, let's not crash here. Change-Id: I5ff49b9b3c326d9005f70a01435c01bfc7307343
* Argh forget to include my final part of the change.Dianne Hackborn2011-01-251-2/+10
| | | | Change-Id: I1e2711e1ecde0350047f1edef9a59947ff5749eb
* Fix issue #3385839: Fragment.onCreateView is passing in activity...Dianne Hackborn2011-01-251-12/+41
| | | | | | ...context for a DialogFragment Change-Id: I434ebca64d2738da4c27321db8dbbded2cbe167d
* Fix a bunch of API review bugs.Dianne Hackborn2011-01-171-1/+1
| | | | | | | | | | 3362464 API REVIEW: android.content potpourri 3362445 API REVIEW: Fragment transaction stuff 3362428 API REVIEW: Fragment stuff 3362418 API REVIEW: Loader stuff 3362414 API REVIEW: android.content.pm.ActivityInfo Change-Id: I6475421a4735759b458acb67df4380cc6234f147
* Start renaming FragmentTransaction.openTransaction() to beginTransaction().Dianne Hackborn2011-01-171-2/+2
| | | | Change-Id: Ib4a6d824b33cca699b7b25159c491fb610d5f5da
* Add "min size" facility to the Window class.Dianne Hackborn2011-01-121-10/+0
| | | | | | | | | | | | | | | | | | | | | | | This allows us to have a new dialog theme that behaves like an alert dialog for both Dialog and Activity versions. Very useful with so many more things being displayed as dialogs on our nice large screen. Note I didn't change the existing dialog themes to have this behavior, since it will probably break things. Instead there is a new variation. And the DialogWhenLarge variations now use this for their dialog form, to fix many of the real new dialogs we have that need this behavior. Removed the public definition of the one alert dialog theme. None of the others have ever been public, this one shouldn't be. Added new .Panel versions of the Holo themes, like we already had for the original themes. Changed the alert dialog layout to no longer use WeightedLinearLayout, since the window now takes care of that. This allowed for the removal of the xlarge version of those layouts. Change-Id: I0c8372bde25eb9af47404a719b3f07230baf73bf
* Implement issue # 3255887 could CursorLoader offer...Dianne Hackborn2011-01-081-1/+1
| | | | | | | | | | | | | | | | | | ...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 animations to use correct interpolator.Dianne Hackborn2010-11-081-1/+5
| | | | | | Also some fragment fixes. Change-Id: I3906199e541a86379d07c8a4e4d5f9e99830c44a
* Fixe some stuff.Dianne Hackborn2010-11-081-2/+10
| | | | | | | | | | | | | | | Addresses these bugs: 3061847 - With no headers, PreferenceActivity crashes 2888426 - minor typo in DevicePolicyManagerService.ActiveAdmin.writeToXml() 3159155 - IllegalStateException:"Can not perform this action after onSaveInstanceState" while dismissing a DialogFragment 3155995 - PopupWindow.showAtLocation does not respect LayoutParams Also tweak the new fragment APIs to use abstract classes instead of interfaces as base classes. Change-Id: I9c0b4337fe0e304b737b5f7c2762762372bb3020
* Holo themes and assets in progressAdam Powell2010-09-271-1/+1
| | | | Change-Id: Ic10480dc1c771d0ccd10f1d4014c945480fd6c0d
* Work on DialogFragment and docs.Dianne Hackborn2010-08-201-16/+183
| | | | | | | | | | | | - DialogFragment now has an option to not show a dialog, so you can use your UI somewhere else. - Deprecated show() versions that were tied to activities. - Added documentation to DialogFragment class. - Added documentation to onSaveInstanceState() to explain how the time it is called is different than Activity's version. - Fixed some java doc warnings. Change-Id: If026744c368e2443030d2d9e0a9c808d820857df
* More fragment work:Dianne Hackborn2010-08-151-13/+26
| | | | | | | | | | | | | | | | | | | | | | | | - Introduce FragmentManager as a public API, deprecating the fragment APIs on Activity. (They will be removed soon.) - Add APIs to write a fragment reference to a bundle and later retrieve it. - Add Fragment API to set another fragment as its target, for delivering results. - Change when onInflate() is called and formalize its meaning in relation to the fragment arguments that were previously introduced. - Change onDestroyView() to always be called, regardless of when onCreateView() returns. It now also is called slightly differently, after the view hierarchy's state is saved. - Fix some issues with DialogFragment's lifecycle with its associated Dialog and state save/restore. - Preference can now have a Bundle associated with it to provide arguments to a fragment. The data for this Bundle call be supplied via <extra> tags under a PreferenceScreen. - PreferenceActivity's header XML tags are now <preference-headers> and <header>, and you can supply <extra> tags under a <header> to set arguments for the header's fragment. Change-Id: I22c212c9fa862d50840201ca16e51f9de5ef0031
* Fix build: tweak documentation linksJean-Baptiste Queru2010-08-131-4/+4
| | | | Change-Id: I9c9c8615086b7173f4ad68b5183e7699275c7a2d
* Fragment and PreferenceFragment and FragmentManager, oh my!Dianne Hackborn2010-08-121-3/+4
| | | | | | | | | | | | | | | | | - Introduce FragmentManager public API, for all Fragment management needs. Will in the future allow the removal of the (growing number of) fragment APIs on Activity. - Fragment now has a concept of arguments. This can be supplied immediately after creation, and are retained across instances. - PreferenceActivity now has an API to have it update its headers (note not tested). Headers now have arguments. Keys for controlling when PreferenceActivity shows at launch have been added to the SDK. - Fixes to back stack handling and state saving/restoring. Change-Id: Ib9d07ae2beb296c4eb3a4d9e1b3b59544675e819
* Add new DialogFragment class.Dianne Hackborn2010-07-241-0/+277
For all your Dialog needs. Change-Id: I36c602ca253488d34a55c8f0be610b9752c33264