| d805095048f6be52cddbd572ee343c4639ba8187 |
|
22-Apr-2016 |
Alan Viverette <alanv@google.com> |
Clean up deprecation tags in support libraries
Also fixes renderscript and recyclerview docs builds.
Bug: 28339627
Bug: 28073702
Change-Id: I0f38cf82fe260de4488660c87aaed8d26265eeba
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| 5fa6d3dd3f408ceb2ff7368fd0259713d9382ad8 |
|
30-Mar-2016 |
Andrii Kulian <akulian@google.com> |
Add PIP and MW mode change callbacks to support library
Bug: 27365860
Change-Id: I903062d3e93882a2503cf080b9f4086c55cc2038
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| c077b4cd990a9f220a27ad5eca04828e17136064 |
|
14-Jan-2016 |
Adam Powell <adamp@google.com> |
Permit setRetainInstance(true) on nested fragments
Save arbitrarily nested fragments across config changes as
nonconfiguration objects. This permits the use of retain-instance
child fragments as arbitrary opaque dependencies within other
fragments.
Change-Id: Id4f216bdc2ccbfba6410661626329f07b5015349
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| a76a4339be2f27431a167381187c3f0b0d08f1b7 |
|
29-Jan-2016 |
Daniel Resnick <danielresnick@google.com> |
Allow onActivityResult(...) to be dispatched to nested Fragments.
This fixes https://code.google.com/p/android/issues/detail?id=40537
by allowing onActivityResult(...) calls to be dispatched to the
correct Fragment even if it is nested in another Fragment.
Change-Id: I4b80c2eb1a83de93b95cb26feca5052aa55c9961
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| 64ece2df3d6d789f7a642692acbe85fa1b998d6b |
|
20-Oct-2015 |
Todd Kennedy <toddke@google.com> |
Retain fragment loaders
Remove the partial fix [it did not work for child fragment managers]
and replace with a more general fix that works with all fragments.
Bug: 23838271
Change-Id: Idf7decd64e344013df63359edd2d4268645eb99c
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| 641da2788e39dcbf17e99ae60c011500d6c5822d |
|
10-Sep-2015 |
Todd Kennedy <toddke@google.com> |
save "retain loader" state
We cannot pull the "retain loader" state from the Activity; an Activity may
not always be hosting a Fragment. Instead, save the "retain loader" state
inside the individual fragments.
Bug: 23838271
Change-Id: Ie5033be06e46488a1ecd6ee18433b1bd737be7f6
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| 8491eb62f621cd5de4b4caed839be09c77011f53 |
|
30-Apr-2015 |
Todd Kennedy <toddke@google.com> |
Sync API with platform
While going through the main platform review, there were several
changes to class and method names. Apply those changes to the
support library to maintain parity with the platform.
Bug: 19569096
Change-Id: Ibe36a664c40379665e3482f792220d975974abca
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| edaa101bfa72b5e5a5b14b9e6c66579eaed5e8cc |
|
13-Apr-2015 |
Todd Kennedy <toddke@google.com> |
Make fragment host usable
There were some limitations in the API of the fragment host. This
should address them and allow the creation of a replacemnt fragment
host.
* added getHost() method; this is akin to the getActivity() method
and allows fragments to get a reference to their host. For the
FragmentActivity host, this method will return the same value as
getActivity()
* made all methods in FragmentController 'public'. This was an
oversight. There should be no package private methods in
FragmentController.
* removed "final" keyword from Fragment#getContext(). While this
method should be final, "getContext()" is too generic/common and
likely to be defined in existing Fragments. We're removing "final"
from the declaration to preven compile-time errors in legacy code.
Bug: 19569096
Change-Id: Id54e5febfdf2b2525c165ebb23f370f71f0ed0b8
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|
| d608cf6e08769bf320c1b595cbbd9a7664160449 |
|
26-Mar-2015 |
Todd Kennedy <toddke@google.com> |
Remove dependency upon FragmentActivity
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: 19569096
Change-Id: I62dee733a70577d0d3c8f96a89e4b05a3d5e18b0
/frameworks/support/v4/java/android/support/v4/app/FragmentController.java
|