| 0d55bf3f07eab80252237d017261249bb6826c84 |
|
05-May-2012 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Refrain unnecessary flicker caused by cross-fade effect
The problem happens when there's no contact photo, in which
BitmapDrawable for the same Bitmap is created every time (for
convenience. Ideally we shouldn't). The problem is that AnimationUtils
is not aware of the fact. This change will check that case too.
Bug: 6406492
Change-Id: I4106751d80af2f61d952ca545fd22db44c6fd6c9
/packages/apps/Phone/src/com/android/phone/AnimationUtils.java
|
| 812dbdb13abbe2d8a9951f8683f84fa14b1c99ef |
|
25-Apr-2012 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Fix proguard.flags
Current configuration will keep all the classes, which isn't expected.
Also, use -verbose as Contacts is already doing.
Change-Id: I55ad402c84e99f17e4ceab730cb3818e7d8d98ac
/packages/apps/Phone/src/com/android/phone/AnimationUtils.java
|
| a84a05e92fca88e677a5c9c08885d7d9e914c7d5 |
|
13-Apr-2012 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Introduce CrossFadeDrawable
This is almost a workaround for bug 6300562 "After splitting call in
manage conference screen, one contact picture may not become that
person's one but still conference's one."
It hapeens when the caller has a conference call with two destinations
and split the call by choosing the second person. At that moment the
animation transition becomes weird in some manner. It won't happen (at
this moment) if the first person is chosen there.
This change will reduce the headache by resetting the intermediate
drawable to the correct one. Wrongly made drawable is cleared at the
last step of the animation, and user will see the correct picture
eventually, while the cross-fade animation is still weird in the case
above.
As a side effect we can have a callback which is consistent with the
other part of the animation util we have so far.
Bug: 6300562
Change-Id: I418afcddb890025b3e3297747a4ff13a2959f65d
/packages/apps/Phone/src/com/android/phone/AnimationUtils.java
|
| 70d1ce9eef69c9a1b81778a4a42a85462e94c3da |
|
13-Mar-2012 |
David Brown <dab@google.com> |
Fix typo in javadoc on Fade.hide().
Change-Id: I5e082155152ac2f88247a4172ff3bc6f5ac07f55
/packages/apps/Phone/src/com/android/phone/AnimationUtils.java
|
| 99868b420062de23c76550a36afdd5f4f6122495 |
|
01-Mar-2012 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Introduce better animation for incoming-call widget
- Place incoming-call widget before in-call controls.
After a4fc0c71, we show both during incoming-call widget is
fading out. In that case, the order becomes important; we need
to show buttons beneath the fading widget. Views are drawn in
order in each layout.
- Use Animator instead of Animation.
We cannot use AnimationUtils.Fade for this case because we need
to override listener. Because of that we also need to introduce
mIncomingCallWidgetIsFadingOut boolean flag.
Bug: 6096473
Change-Id: I08ff9084db14256879a3ec706dcc3a4febbdcb84
/packages/apps/Phone/src/com/android/phone/AnimationUtils.java
|
| 0f3a4bfe3a9a3aed224a9c89b82c986cd12c3fe8 |
|
01-Mar-2012 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Introduce AnimationUtils
- move CallCard.Fade to the new class
- have startCrossFade() method for ImageView
Bug: 6077015
Change-Id: I8a3999e35fd37f98c8bff553cc1442a7ba4e4647
/packages/apps/Phone/src/com/android/phone/AnimationUtils.java
|