| c766ad5a6e0c115f08b933ede22375c7070a3391 |
|
31-Oct-2014 |
George Mount <mount@google.com> |
Only modify add Transition targets when they aren't targeted.
Bug 18191727
Transitions were targeting specific views, but they do this by
adding targets. If there was already a view targeted, now that
transition also targeted a different view. This prevents that
by only targeting views when no target was given.
Change-Id: I003d531c6d249e5fdec5a544d37220350838bb3a
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 62260534040eba52462875a435df2c1f50ab846e |
|
19-Sep-2014 |
George Mount <mount@google.com> |
Target only shared elements with shared element Transition
Bug 17549213
Bug 17553253
Change-Id: I82b9f52fdd8b386abd5839e1471fab82f890b327
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 983592c887664932c3b27433ef9fb1ff191a7972 |
|
19-Sep-2014 |
George Mount <mount@google.com> |
Merge "Fix exception when fragment container has no View." into lmp-dev
|
| 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/BackStackRecord.java
|
| 8dfd79ec7028cfdfa1ba69ed7cbf27aac41dc78a |
|
18-Sep-2014 |
George Mount <mount@google.com> |
Fix custom animations disabled always.
Bug 17549252
Custom animations should only be disabled when fragment transitions
are running.
Change-Id: I8ec0bc9b90ce7d149b1c5fe25363bb5e7bbe315b
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 5a8f14de0bb4304f9a3aebdcb35ee0dd607f27f7 |
|
15-Sep-2014 |
George Mount <mount@google.com> |
Fixed enter/exit transitions working against shared elements.
Bug 17499971
The enter and exit transitions were targeting the shared element.
This means you'd get double transitions on the shared element.
Fixed bug where the wrong views were targeted when there was
only one enter/exit/shared element transition.
Change-Id: Ieb3a4cfcd35479a82adc3ee269c5b0015ab5d5af
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 6739bc7f97ba5486b6f6114fb3812b098822cc3c |
|
10-Sep-2014 |
George Mount <mount@google.com> |
Merge "Move capturing entering views until just before transition." into lmp-dev
|
| 0f5ae57910484f1d873fdad90966b6244a633bd4 |
|
08-Sep-2014 |
George Mount <mount@google.com> |
Move capturing entering views until just before transition.
Bug 17407387
Bug 17420256
Recycler view doesn't instantiate its views until after
the onCreateView call. This delays the capturing of
final views until just before the entering state is
captured for the Transition.
Change-Id: Ifd6ecaa21cefb4f6f8f720b319993bf0b9e2d8f7
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| a52784195525cdb1f2bb4d8dde1b8b314f480957 |
|
10-Sep-2014 |
Chet Haase <chet@google.com> |
Remove references to "L"
Issue #16894783 Remove references to L when API is locked down
Change-Id: Icf1215eed34e6fbe3d71a5cec4bf1699c3bc3ff9
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.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/BackStackRecord.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/BackStackRecord.java
|
| 128bb5c66d0b34c5a658c682deb3a0b9199b20c4 |
|
22-Aug-2014 |
George Mount <mount@google.com> |
API Review: change fragment transition methods.
Bug 16959326
Change-Id: Ie0aea3b3a6fd432ca061d8bf8a245e0a3ec25e99
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 4500be62dea3895a98336122a2944cc4ab024bc5 |
|
27-Jun-2014 |
George Mount <mount@google.com> |
Add support for shared elements in fragment transitions.
Bug 15891071
Custom transitions in the Fragment Transaction have a
higher priority than animations, transition style, or
transition resource. If the API < 20, custom transitions
will not be active and the other animation types will
take effect.
Change-Id: I7f18f9b9a75f73d58a16184a301458bdcd331098
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| 3a7571011a8f2c2e2685c4e3e7a6fa46673ee7ea |
|
27-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #7232641: ISE crash when rotating phone in label list mode
This doesn't fix the problem; I think it is an app problem. It does
improve a bunch of the debugging to help better identify what is going
on, and introduces some checks when adding a fragment to fail
immediately if we are getting into a state when a fragment is going to
be in the added list multiple times (which is pretty much guaranteed
to lead to a failure at some point in the future).
Change-Id: Idac978eb6bd2bd38d54e50532907c40b264ac300
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.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/BackStackRecord.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/BackStackRecord.java
|
| df6f1393f73a488ba2661b28d3d88a5ac19c4ea2 |
|
26-Jul-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #5063010: Loaders don't seem to be properly...
...retained with compatibility library
Also we never implemented the full custom animation stuff in the support
lib. Now it is there.
Change-Id: I25b410752fdc3e7ae876802fdc8d7a62e4b07236
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| eedc67283a5a49dce86c625e54596dfdea9465a7 |
|
05-Apr-2011 |
Dianne Hackborn <hackbod@google.com> |
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.
Change-Id: I997492cfc6f1969f1a5d775385afb830f5a47795
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|
| cba2e2c881e8e16ea5025b564c94320174d65f01 |
|
08-Feb-2011 |
Dianne Hackborn <hackbod@google.com> |
First checkin!
Change-Id: Ib09737c48a144dd778efe4750452d74ac8265a29
/frameworks/support/v4/java/android/support/v4/app/BackStackRecord.java
|