e9d32ea13ee14fc0eb4e45ca627ca77729d38bfe
The behavior of running a transition is janky and unpredictable, when there is already a transition running on the same scene root. Usually, the new transition simply jumps to the end values, or jumps to the start values for that transition and animates from there. A better approach is to cancel any running transition first, the start the new transition from that point. Even better would be to blend old/new transitions, or at least adjust the animation timing according to where/when the previous transition stopped. In the meantime, this fix is at least better than the previous approach of ignoring running transitions. Change-Id: I4f5fabb55f6454f1e9d66589a9a7c36f9fc013fb
am
3c080baa: am 564889b1: am 4a024be4: am 4cef8150: Merge "update dashbord for 6/3" into jb-mr1.1-ub-dev
am
c41a0eff: am be22605d: Merge "Listen for HTTP proxy changes and propagate the information to the media" into jb-mr2-dev
cherrypick from ics-mr1 docs: source for nw app Change-Id: If50f407a0e56fa802fe9beedaa650e3a131872b2
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%