| ab42aec4bc0311b2d36aaa85ad73dd91768d7e4c |
|
07-Nov-2013 |
Adam Powell <adamp@google.com> |
Fix docs
Change-Id: Iaeef1812e3dfa76abe40468066860f73d8a10f79
/frameworks/base/core/java/android/transition/Scene.java
|
| 18e905f42d017c4721d33bd25d7d39ef8d64b5d5 |
|
24-Oct-2013 |
Adam Powell <adamp@google.com> |
Make Scenes and Transitions first-class in PhoneWindow/Themes
Add a window feature for content transitions. This implicitly creates
a Scene for each setContentView operation and runs the appropriate
transition. Applications can specify a TransitionManager XML in their
theme that will apply the appropriate transitions when these implicit
scene changes occur. Apps can specify a "to" with no "from" in a
transition to request an entrance transition for the given
content. This lays the groundwork for further full content
change/activity to activity transitions.
Change-Id: Ic815d9e0b9ce958152d70bf6ee01be075aa9fe88
/frameworks/base/core/java/android/transition/Scene.java
|
| f3c157721260b3cfc45874fc4f613ba2bd2e7f9e |
|
25-Oct-2013 |
Adam Powell <adamp@google.com> |
Fix bug in Scene's use of setTag
setTagInternal must be used for framework resource IDs.
Bug 11374402
Change-Id: If4d256dbf05055dac70796edd8d7b94bf65d947d
/frameworks/base/core/java/android/transition/Scene.java
|
| 40a67888f91c2bb94c8654fbfe402f84795d17cf |
|
23-Oct-2013 |
Adam Powell <adamp@google.com> |
Cache Scene objects by layout ID on the scene root
The current tracking of scene objects in a static ThreadLocal is
problematic as it leaks the Context associated with the SceneRoot and
returns the wrong Scene object if the same layout ID is used across
different scene roots.
Track Scene objects on the scene root view instead to avoid these
issues.
Change-Id: I891986897f757f2666897c937b5ebb0ed1d531c1
/frameworks/base/core/java/android/transition/Scene.java
|
| b7a7fc9d233bad507ce893882352618b13647058 |
|
21-Sep-2013 |
Chet Haase <chet@google.com> |
Make fading transitions work better
Previously, a Fade transition would only affect a view if its
parent hierarchy was not also affected between the start/end states.
This caused problems for views which were removed from their parents
between scenes when their parents' visibility also changed between those
scenes. The effect would be that the transition would fade the parent...
but the child would no longer be in that parent, so the user would just see the
child view blink out.
This fix ensure that views are faded appropriately by fading them
regardless the parent hierarchy; if a view is removed from its
parent, fade it out.
Additionally, if that view has not been removed from its parent, but
its parent is no longer parented *and* scene being
transitioned from is based on a layout resource file (and thus
the views are considered temporary after transitioning), then it is
removed from its parent to be faded out in the overlay.
Also, renamed TextChange to ChangeText to be more consistent with
other transition class names.
Change-Id: I4e0e7dfc9e9d95c7a4ca586534b6d204c4f3bae0
/frameworks/base/core/java/android/transition/Scene.java
|
| d82c8ac4db7091d2e976af4c89a1734465d20cd2 |
|
26-Aug-2013 |
Chet Haase <chet@google.com> |
Transition API changes from API council recommendations
Issue #10460684 KLP API Review: android.view.transition and android.animation
Issue #10570740 Transitions: inflate transition targets from xml
Change-Id: I7a3f6d3aece2fcafc5efd555d033f79e86635c98
/frameworks/base/core/java/android/transition/Scene.java
|