| cef09fee2126f901aa164f6e89c370ab81cff1b3 |
|
13-May-2016 |
Adam Powell <adamp@google.com> |
Add Fragment#onAttachFragment for parent fragments
Add a matching onAttachFragment method to Fragment to match the
fragment host version.
Bug 28760393
Change-Id: I1dbcc336e4f191717add0dc83d48db93baa953fa
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| fd15fbacc1d0cb92f2edf72137e4940be2547aa4 |
|
11-May-2016 |
Adam Powell <adamp@google.com> |
Less lazy child FragmentManager creation
Fix a bug where child FragmentManagers moving too lazily into the
CREATED state and beyond caused child fragments to not be
attached/created when expected.
Bug 25019275
Change-Id: Ia16f6d9075e6b611d3363ad1eac6408b896604bb
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| f7bdb2b37497128b8a9108eea43c17ea544c957a |
|
22-Apr-2016 |
Alan Viverette <alanv@google.com> |
Merge "Clean up deprecation tags in support libraries" into nyc-dev
|
| 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/Fragment.java
|
| 916455675ddb34d0eb848b2355550268d82c3ce7 |
|
21-Apr-2016 |
Adam Powell <adamp@google.com> |
Move child FragmentManager shutdown for retained fragments
Support lib edition
Some apps out there do some creative things in terms of calling their
own onDetach methods from elsewhere. Perform the child FragmentManager
shutdown for retained fragments in a package-level perform method
instead of in onDetach itself.
Also mark all existing fragment methods with @CallSuper.
Bug 28293847
Change-Id: I5cad21589d1794034d0fd63aaf45dd2984d3c8cc
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| fed04169c31e7e3d8c7a328876358dd3564062bb |
|
14-Apr-2016 |
Clara Bayarri <clarabayarri@google.com> |
Provide startIntentSenderForResult for fragments
Bug: 27700608
Change-Id: I43139604b0aa60c2dcce93db92a38e1327566a4e
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 3ab5a96f51cbd0498a62f1e91f1ef99e95cb1b1c |
|
06-Apr-2016 |
Adam Powell <adamp@google.com> |
Fragment#setUserVisibleHint guard
Bug 28026606
Change-Id: If3c23a4a54c32790e459ed61881870dcf27d7c51
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| c83dccecb0ec4bf9f4befdb18caccb8f373ed7bc |
|
02-Apr-2016 |
Adam Powell <adamp@google.com> |
Don't performPendingDeferredStart on fragments that aren't added
When setting a user visibility hint on a fragment it was possible to
have a FragmentManager already set due to a transaction being composed
but before the commit, so only checking that we have one isn't
sufficient for determining whether we should perform a pending
deferred start. This could happen easily with ViewPager adapters. Use
isAdded() instead.
Also fix a bug where we could set our internal tracking of fragments
that need a deferred start incorrectly.
Bug 27814550
Change-Id: If288720d998ecfa69d5e18aad5ce33075013754e
/frameworks/support/v4/java/android/support/v4/app/Fragment.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/Fragment.java
|
| 9375145b63d854c64aad99e6e50c5b7e5ba32b95 |
|
03-Mar-2016 |
Adam Powell <adamp@google.com> |
Fix bugs around restoring nested retained instance fragments
In a few configurations the child fragment state of a
retained-instance fragment would not be preserved correctly, leading
to child fragments not being restored. Clean this up along with live
state management issues that were leading to logged warnings during
normal fragment operation.
Bug 27371492
Bug 27477824
Change-Id: I6e86a7f0c158b7dea17b5c8d2b8275e3842b178b
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 95b47440a7a8417c7e4000c82bda81ed57279725 |
|
01-Mar-2016 |
George Mount <mount@google.com> |
Merge "Clear child fragment manager after it is destroyed." into nyc-dev
|
| e921ce103054105d4325e80fb9d3999550bbeb2e |
|
19-Feb-2016 |
Adam Powell <adamp@google.com> |
Fix a NPE with Fragment#setUserVisibleHint
Fix a bug where calling setUserVisibleHint(true) before a fragment is
attached to a FragmentManager would throw NPE. As the same fix has
been made in frameworks/base, adjust FragmentCompat to guard against
the pre-existing bug in older platform versions.
Bug 27250018
Change-Id: Ifc72f2f16e728414e3ecd80fd34b933bcad73729
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 4706c089880423ee5929d4635c6dfc5c3151b20f |
|
17-Feb-2016 |
George Mount <mount@google.com> |
Clear child fragment manager after it is destroyed.
Bug 26945643
After a child fragment manager has been destroyed, it should not
be reused because it is no longer attached to the host. Clearing
it ensures that it will be recreated when it is needed again when
the fragment has been reattached.
Change-Id: I579abf570beb62df3c3fd5ade3b74506f304b2aa
/frameworks/support/v4/java/android/support/v4/app/Fragment.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/Fragment.java
|
| fa5efe434be3e33f05cc59c402ca34165d15cf7f |
|
14-Jan-2016 |
Adam Powell <adamp@google.com> |
Merge "Init child fragments consistently with activity fragments"
|
| 9361479b836539a22afdb5587dc81680f9d0401b |
|
14-Jan-2016 |
Daniel Resnick <danielresnick@google.com> |
Merge "Support launching activities with animations from Fragment." into mnc-ub-dev am: b3969e252b
am: 962050ba63
* commit '962050ba632f95d8d8e86183c213063023cc0ea4':
Support launching activities with animations from Fragment.
|
| b3969e252bb1d048b2f97177529b375d753e51ca |
|
14-Jan-2016 |
Daniel Resnick <danielresnick@google.com> |
Merge "Support launching activities with animations from Fragment." into mnc-ub-dev
|
| 277f9d9ad10cd8e989619ee51c888761029daa98 |
|
14-Jan-2016 |
Adam Powell <adamp@google.com> |
Init child fragments consistently with activity fragments
Fragments contained within an activity are restored from instance
state in FragmentActivity.onCreate, but fragments contained within
another fragment were previously restored from instance state in
performCreate after onCreate returned. This meant that developers
couldn't consistently rely on being able to control when this happens
with a call to super.onCreate, and calls to findFragmentByTag to
reconnect with a restored child fragment would fail in ways that
succeed when the fragment is directly added to an activity.
Change child fragment instance state restore to happen during
Fragment.onCreate instead of in performCreate to be consistent with
activity behavior.
Change-Id: I86f70c4e03c428598bb7803fe226ae3e58c82cc4
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 0e35b9f59703416786e7ac460726c2c06a9194fc |
|
09-Jan-2016 |
Daniel Resnick <danielresnick@google.com> |
Support launching activities with animations from Fragment.
Change-Id: I03eb17d2385fad9e5bfda76889316b5407d7dede
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 2913b112d6089ea3e7ebe4a807394dd99f3ebc0f |
|
12-Jan-2016 |
Adam Powell <adamp@google.com> |
Eagerly update fragment state when moving between states
Previously we would not set a fragment's new state until the move to a
new target state was fully complete. This causes problems when other
parts of the fragment manager infrastructure (such as lazily
initializing a child fragment manager) read that state while we're
dispatching a state change call to a fragment.
In this situation, adding a child fragment and then calling
executePendingTransactions on the child FragmentManager would not have
the intended effect, as the child FragmentManager would still be in
state INITIALIZING. The expected lifecycle callbacks to the child
fragment would then occur later.
Fix this by updating the fragment state as we go through each phase of
moveToState before we dispatch to the associated onState method,
matching our usual pattern of invoking onFoo methods after foo has
occurred. Delete the redundant resumed field as we now can use the
state directly.
Bug 25019275
Change-Id: Ia637c4d67f3752e8dd591ed9a53a783690e41d80
(cherry picked from commit 20735a45289fdad3d5d31228992e0dccd3d5dd4f)
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 20735a45289fdad3d5d31228992e0dccd3d5dd4f |
|
12-Jan-2016 |
Adam Powell <adamp@google.com> |
Eagerly update fragment state when moving between states
Previously we would not set a fragment's new state until the move to a
new target state was fully complete. This causes problems when other
parts of the fragment manager infrastructure (such as lazily
initializing a child fragment manager) read that state while we're
dispatching a state change call to a fragment.
In this situation, adding a child fragment and then calling
executePendingTransactions on the child FragmentManager would not have
the intended effect, as the child FragmentManager would still be in
state INITIALIZING. The expected lifecycle callbacks to the child
fragment would then occur later.
Fix this by updating the fragment state as we go through each phase of
moveToState before we dispatch to the associated onState method,
matching our usual pattern of invoking onFoo methods after foo has
occurred. Delete the redundant resumed field as we now can use the
state directly.
Bug 25019275
Change-Id: Ia637c4d67f3752e8dd591ed9a53a783690e41d80
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| f66f3fc0d234015edbd86952c3e3520001858e55 |
|
20-Oct-2015 |
Todd Kennedy <toddke@google.com> |
Merge "Retain fragment loaders" into mnc-dr-dev am: f79417e198 am: 6415ff3a73 am: c3af4b26a0
am: 920e878e98
* commit '920e878e98040f570b4d17e4a8ea9a4086d0ed66':
Retain fragment loaders
|
| 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/Fragment.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/Fragment.java
|
| a56ddd802682129b7a5ebd895a2b13ef7a799c5b |
|
21-Sep-2015 |
Todd Kennedy <toddke@google.com> |
Merge "save "retain loader" state"
|
| a8fa6b4ae84487c5669944cf758c24095c68847e |
|
21-Sep-2015 |
Todd Kennedy <toddke@google.com> |
Merge "Save Fragment's hidden state"
|
| 2750390fbdc2e7037a7e10141d23f2068ae8c2d7 |
|
21-Aug-2015 |
Svet Ganov <svetoslavganov@google.com> |
Update requestPermission docs about requesting a held permission - support
bug:23370436
Change-Id: I89b13ff55b5a30a45cf2cebcca6096c206ab4d60
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 2bdd09a243b422960168170e2344274cc9cfd788 |
|
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/Fragment.java
|
| 340a183c3293d98842e4a2671b500e8e80258818 |
|
23-Jul-2015 |
Todd Kennedy <toddke@google.com> |
Save Fragment's hidden state
Bug: 22666353
Change-Id: Ia263bf664274479354c1ab79917078c0ea07696e
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| dddb7e2bbb343ecb435026c13028ba5cd1ae42a5 |
|
17-Jul-2015 |
Svet Ganov <svetoslavganov@google.com> |
Improve documentation of onRequestPermissionsResult
bug:22524902
Change-Id: I5b27b30d9e97513663afff71c77c0c4d751fef73
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| e1e957f536c20ebe2a7e6c417ccb2fd8f7fa845b |
|
11-Jun-2015 |
Svetoslav <svetoslavganov@google.com> |
Add v4 support for permission APIs on fragments
Change-Id: I5a4abba0f65f5f92632c0031b0f7c259d5c61024
/frameworks/support/v4/java/android/support/v4/app/Fragment.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/Fragment.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/Fragment.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/Fragment.java
|
| bf0947be2ead9b3d8e5865bcd3d3652d02a2aa5a |
|
11-Mar-2015 |
Chris Banes <chrisbanes@google.com> |
Fix compat child fragment inflation
Was caused by AppCompat using a Factory2, which trumps
the Factory that FragmentManager was using. Fixed by
making sure we use a Factory2.
BUG: 19666640
Change-Id: I2f321da756a361ab7ed31aed65f0f8ce1f0d8bcd
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| c861fd8b28b0b878ccc194ee6099b3b1bc4c3ae8 |
|
23-Feb-2015 |
Scott Kennedy <skennedy@google.com> |
Mark some methods/parameters @Nullable
These now match the corresponding classes in android.app.*
Change-Id: If20c32636a5e64a9a64dadb0001983bd2bd3b850
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 0fb3ec354da6c1f3ed1777bca5270710cc537e92 |
|
14-Feb-2015 |
Scott Kennedy <skennedy@google.com> |
Mark findViewById(int) @Nullable
Change-Id: I9dff1548dd1cd5f0ce69bec3a47a4153de034458
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 7516316ffdf6fbf7b248c615404831191daa66a4 |
|
18-Sep-2014 |
George Mount <mount@google.com> |
Fix exception when fragment container has no View.
Bug 17535259
Change-Id: Ic58886e93557b8894d4754597889bd29476259de
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| b1413bc4de16e05ae0455cad93f1edfbcc4eced2 |
|
12-Sep-2014 |
George Mount <mount@google.com> |
Changed method name to match Activity's method name.
Bug 17488968
Change-Id: Idf9957b003940464d86ac7fcfa530a9b2dfcaf47
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 362e45b58bee02699f046ed1b4492e5808837f64 |
|
05-Sep-2014 |
George Mount <mount@google.com> |
Fix build break.
Change-Id: I3d41f20a8cb7f84e6c906b005b0c51318f5323f5
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 9306f07b1d66f4974a81f781d29739b30124fff0 |
|
29-Aug-2014 |
George Mount <mount@google.com> |
API Review: change SharedElementListener to SharedElementCallback
Bug 17289526
Change-Id: I49f8d838207524fbf0ec099021bcf7312c28bd82
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 9f4a046cbeb22a24d322a644323b41022ad9d15a |
|
02-Sep-2014 |
George Mount <mount@google.com> |
Change Fragment Transitions to match Activity Transitions API.
Bug 17188255
Change-Id: I99897ba3c78f3f140000a719afbcfac951e43290
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 0f3dfb28a503b3fb3e51666dd565b0d17eaebfbb |
|
14-Jul-2014 |
Adam Powell <adamp@google.com> |
Port of nested fragments patch
Nested fragments - fragments inflated from within another fragment -
are now added to the containing fragment's child fragment manager
instead of the Activity's fragment manager.
Bug 12763389
Change-Id: I32b3322c9b6344c69f2fefc6e443b656b5f8fc5b
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 5e8ef0460dfca1e3806b491fa886995baf0cfe9c |
|
29-Apr-2014 |
Tor Norbye <tnorbye@google.com> |
resolved conflicts for merge of a3ff3273 to klp-modular-dev
Change-Id: Idc0fdf6c997ef63c14e4d8df417d1179cdcb1403
|
| a3ff3273e976adf19770651dcf473fa67b38eb22 |
|
21-Mar-2014 |
Tor Norbye <tnorbye@google.com> |
Add tools metadata annotations to the support library
Change-Id: I018ccee411da848e6ced91da316f86ae149dc218
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 6252d78085a07c9d6bb4645a4e8086bf23b0a49a |
|
28-Feb-2014 |
Tim Kilbourn <tkilbourn@google.com> |
Clear child FragmentManagers when destroying Fragments.
If Fragment has instantiated a child FragmentManager and is later
detached, it retains its reference to the child FragmentManager which
has been destroyed. This causes an IllegalStateException in the
child FragmentManager if the original Fragment is reattached.
Fixes Issue 42601.
Change-Id: I62155a535948a73bbbc09aefc2b15cfad58b9233
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 2c53644e27f4d989b87381cdd05a037e8d98d1d4 |
|
09-Aug-2013 |
Adam Powell <adamp@google.com> |
am 7367fd6f: am 3fafb081: Pick which kind of fragment to inflate from <fragment> tags
* commit '7367fd6fb5ec7d30d36711d1115f18d4a50b9f0e':
Pick which kind of fragment to inflate from <fragment> tags
|
| 3fafb0817f980d1819d0708b3c3da00454ba4c1f |
|
09-Aug-2013 |
Adam Powell <adamp@google.com> |
Pick which kind of fragment to inflate from <fragment> tags
If an Activity extends from FragmentActivity the LayoutInflaters
obtained from it were previously be configured to parse <fragment>
tags exclusively referring to android.support.v4.app.Fragment class
names. Have FragmentActivity delegate this to the underlying device
framework to allow the use of android.app.Fragment fragments in
layouts.
Bug 10258465
Change-Id: Ic4274657b079fbf61ddf0f34df2cdec9602fc7ed
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 80f8f434f1a5ee950084d8aedd70135de281df72 |
|
18-Jul-2013 |
Scott Main <smain@google.com> |
am 3cf73a41: am 9dcd2e58: javadoc edits for support library
* commit '3cf73a4119b9b216ea22f796364ed00525ceac41':
javadoc edits for support library
|
| 9dcd2e58138ca4eb4b18f80b50e8979329e859d6 |
|
17-Jul-2013 |
Scott Main <smain@google.com> |
javadoc edits for support library
Change-Id: Ie8f228036dc9d33315430490a2e03e9c504ada71
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 2290993eddf5262a8df7fc9478daed52401e325a |
|
17-Jul-2013 |
Dianne Hackborn <hackbod@google.com> |
Add ArrayMap to support lib.
Also integrate recent container class changes in to
the support lib, and modify activity/fragment to use
ArrayMap.
Change-Id: I9f28c3661b8d9c3de8f8409e721feb1a714e9d1b
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 3a1a7fff9873abbf8097c96f7654a459bf34f223 |
|
19-Apr-2013 |
Jeff Brown <jeffbrown@google.com> |
appcompat: Add plumbing for fragment options menus.
We make the callbacks available through an interface so that
developers can implement them on any fragment without having
to subclass ActionBarFragment.
The plumbing is mainly transparent to v4 support although we
needed access to a few properties.
Bug: 8661191
Change-Id: I1abce746b7b8443efd406a3e1a4b92c948c678db
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| da10fdd1400ecfd8d7f2e55651dd528d0614dfc5 |
|
19-Mar-2013 |
Jeff Brown <jeffbrown@google.com> |
Move appcompat library to v7 package.
Moved most of the options menu related functionality out of v4
support lib into appcompat where it belongs. These two libraries
have very different design philosophies and it is important that
they remain untangled.
The support action bar options menu is broken by this change but
will be fixed in later patches after some refactoring to more
fully express the facade-like nature of the appcompat library.
Collapsed the appcompat eclair, honeycomb and ics folders into
one src folder because the layering did not make any sense.
All of these folders were providing portions of the API.
The layering will be reconstructed and improved in later patches.
Moved implementation types into an internal package within appcompat
to prevent them from leaking into the API.
Changed the base package name to android.support.v7, similar
to the gridlayout support lib.
Bug: 8175766
Change-Id: I538cbe08310e63e96a2a9fed0b8636eeda530f2c
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| e0f27d39b0a4f0ef30ef6446e7b675279961cc94 |
|
28-Feb-2013 |
Chris Banes <chrisbanes@google.com> |
Move support Menu interfaces + callbacks to v4 (DO NOT MERGE)
This moves the Menu* interfaces used for the ActionBar
into android-support-v4. This allows us to remove
ActionBarFragment and related hackery.
This commit just keeps us at the same level of functionality,
but is a cleaner implementation. A future feature would be
to enable the use of the support Menu when not using
ActionBarActivity.
Change-Id: I952ce78a378e8ec3b990f5c285a44c7fc4807f0c
Signed-off-by: Chris Banes <chrisbanes@google.com>
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 5f1309fe533f644638155e79d50e23060191bf59 |
|
20-Feb-2013 |
Chris Banes <chrisbanes@google.com> |
Propogate support menu callbacks to Fragments (DO NOT MERGE)
This commit adds a new Fragment subtype which contains versions
of the support menu calls. A number of changes to ActionBarActivity
have been needed to make this possible:
- ActionBarActivity and related classes have been moved to the
android.support.v4.app package.
- FragmentManagerImpl instance creation has been moved to a method
in both FragmentActivity and Fragment, so that we can return a
new sub-type: SupportMenuFragmentManager
- FragmentManagerImpl is no longer final
- The compat ActionBar menu set up has been changed so that it happens
in onPostCreate. This is so that any fragments can be added in onCreate.
Change-Id: I591ca163762431cae9a4988cd89e0711d6b5ff21
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 0adacc1aa313d757ae1c517152cef838e0f35c13 |
|
09-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
Nested fragments.
Change-Id: I2cfd30fda55320796c8eec738f5b9b592ea2c29c
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 5506618c80a292ac275d8b0c1046b446c7f58836 |
|
05-Jun-2012 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #6584942 IllegalStateException: Failure saving state...
...active SuggestFragment{419494f0} has cleared index: -1
There were issues when the same fragment was removed and then
added again before completely finishing the remove (such as due
to a running animation).
Two fixes:
- Now when you call FragmentTransaction.replace() and are replacing
a fragment with the same fragment, this becomes a no-op, to avoid
visual artifacts in the transition and bad states.
- When we are moving the fragment state up and it is currently
animating away to the INITIALIZED state, we could end up making
the fragment inactive as part of the cleanup. In this case it
shouldn't be made inactive; we just need to initialize it but
keep it active since we are going to continue to use it.
Bug: 6584942
Change-Id: I4c37a8e48b115feb0892ef0eb92316d7aeba7b1b
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| be2c79d9a5439922030d2a3846c81c61f0e16912 |
|
16-May-2012 |
Dianne Hackborn <hackbod@google.com> |
Follow changes in framework.
Change-Id: I424a6e8f4b8b50d421c56bb018beab1063ba2cef
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 0574ca37da4619afe4e26753f5a1b4de314b6565 |
|
17-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Add the support libraries to the platform documentation (support libs).
Updated the support libraries' documentation.
bug:5629339
Change-Id: Ia026696e541ab200ce05601aabe062a303bcbb97
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 79398eaefea45e61d839cf4e0534f0eafee70a09 |
|
07-Nov-2011 |
Adam Powell <adamp@google.com> |
Change the "start deferred" fragment API to "user visible hint" -
Support lib edition
Allow a fragment to set a hint of whether or not it is currently user
visible. This will be used implicitly to defer the start of fragments
that are not user visible until the loaders for visible fragments have
run. This hint defaults to true.
Modify FragmentPagerAdapter to use the new APIs both in
frameworks/base and here.
Change-Id: Idb5bce8a9ddf484186942555cd3c581d833eba7c
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| abc968f1eba800c34a4008deb43b015da5d23a5f |
|
26-Oct-2011 |
Adam Powell <adamp@google.com> |
Defer starting fragments in FragmentPagerAdapter for offscreen pages.
Add FragmentCompatICSMR1 to work with deferring fragment starts.
Fix some slightly dodgy layout behavior in ViewPager when extra child
views are present.
Add deferred start feature to support library fragment/loader
framework.
Change-Id: Ied454a6f3e11024eafc970ed9d091788c2d80bab
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 218c1e661578e2a17928f7dbb590b43d1c79aeb7 |
|
02-Sep-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #5238823, #5100340 and #5249654.
5238823: java.lang.NullPointerException at...
...android.support.v4.view.ViewPager.pageRight(ViewPager.java:1335)
5100340 Leaking reallyStopped in FragmentActivity
5249654 ViewPager resets focus on layout when descendant of...
...fragment.getView() is focusable (FragmentPagerAdapter bug)
Also there was a bug in the "really stopped" thing that was
previously introduced -- fragments wouldn't stop their loaders
until hitting that state, but they wouldn't go into that state
if the fragment was deactivated or put on the back stack without
the containing activity really stopping.
To fix this, we now implement the really stop facility as
an actual state, using the ACTIVITY_CREATED state, so that we
can know when to do the really stop for both cases.
Change-Id: Ia9bd55f41ad30c3ce07f99b6ac6d9113b15fe46d
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 2a4d8518f36346ea25a22a736453ff28f2954165 |
|
30-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issues 5158104 and 4981556 (fragment problems)
5158104: com.android.contacts: java.lang.IllegalStateException:
Can not perform this action after onSaveInstanceState at
android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1201)
The ViewPager can just commit without worrying about a state loss,
since it can correctly reconstruct its state later.
4981556: Fragment.mImmediateActivity doesn't get restored on orientation change
I am giving up on this thing; I just don't see how it can actually
be correct. So now instead of getting an exception about a dup
add/remove at point of the add/remove call, this will happen later when
processing the transaction.
Also add an API for controlling the visibility of menus, which ViewPager
uses to have the correct menus shows. And add a method to get the
name of a back stack entry.
Finally fix a recent problem in ViewPager with dealing with focus,
and make ViewPager smart about handling keyboard focus navigation
inside itself.
Change-Id: I280269ac64079d171e9c899ea1cff7e80246c924
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 2c4b5dbfee5232bcbbcb74b84ce9147b62a9d789 |
|
15-Jun-2011 |
Dianne Hackborn <hackbod@google.com> |
Merge in fixes from main platform.
Change-Id: I8e63b6990022869aa033d4672018d6585355bf76
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 9c53b844bd525e6a04e17291efc38713893074cd |
|
13-Jun-2011 |
Dianne Hackborn <hackbod@google.com> |
Update to follow fixes from platform.
Change-Id: I9918b084426c62a60581e3ac6e69a48e51b7cc9b
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 5c1637087453de15e31861f073eae5133c4e9f7b |
|
06-Jun-2011 |
Dianne Hackborn <hackbod@google.com> |
Move PagerView down to the v4 support lib.
Adds in standard adapters for using PagerView with the fragment support library.
Also bring in the most recent HC fragment API and impl changes so that the support
lib matches it.
Change-Id: Id8a590378b8c544a92df4f3c11af323c930aa5fd
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| e4417c91a0bb2fba42a0aaa99edcca1b238af21a |
|
05-Apr-2011 |
Dianne Hackborn <hackbod@google.com> |
DO NOT MERGE. Integrate support work from master.
First submit of FragmentPager class.
This provides an easy way to build a UI where the user can
swipe left or right through its elements. The elements are
implemented as fragments, and the class takes care of managing
those fragments as the user navigates through it.
This implementation also introduces a new FragmentManager
concept of a "detached" fragment -- basically a way for you
to put a fragment in the same state as when it is on the
back stack, where the framework is managing its current state
but it is no longer actively running.
Also required the introduction of new compatibility code for
MotionEvent and VelocityTracker for accessing multi-touch data.
Tweak view save/restore state so it will play well with list views.
We need to restore the state *after* the adapter has been set;
setting the adapter clears the state. To do this, we move the
state restore from immediately after the view is created to after
we call Fragment.onActivityAttached().
Also introduced a new Fragment.onViewCreated() callback which is
nice for fragments that want to do some setup after onCreateView()
but allow for subclasses to override that method. (ListFragment
I'm looking at you.)
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 9277b9e4419c1f0b5236d9b573a7cc0b23d56402 |
|
09-Mar-2011 |
Dianne Hackborn <hackbod@google.com> |
Implement fragment animations.
I forgot to finish the implementation of this in the support library.
Currently the standard animations are very hard-coded to look the
same as HC.
Also bring over my MR1 fix to onInflate().
Change-Id: Ib584e158bb691986d912aea5fd3004b8b2da7a6a
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| 681a6fb06bdedb8661a68a1b9e34727b6059aa39 |
|
14-Feb-2011 |
Dianne Hackborn <hackbod@google.com> |
Finish remaining key implementation.
Change-Id: Idb10f45bc109e57966dd2abdf446e60c5fd32aec
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|
| cba2e2c881e8e16ea5025b564c94320174d65f01 |
|
08-Feb-2011 |
Dianne Hackborn <hackbod@google.com> |
First checkin!
Change-Id: Ib09737c48a144dd778efe4750452d74ac8265a29
/frameworks/support/v4/java/android/support/v4/app/Fragment.java
|