summaryrefslogtreecommitdiffstats
path: root/native
diff options
context:
space:
mode:
authortiger_huang <tiger_huang@htc.com>2015-04-27 20:36:46 +0800
committerWale Ogunwale <ogunwale@google.com>2015-05-15 10:27:17 -0700
commitb7f3f92ac200fb22cd8d880b63a5c0ef2bad5354 (patch)
treeb861cad553187d3c698a199ea9440e05e3896a69 /native
parent0c72f4f9d04077f2fe96b486b8501303325a54af (diff)
downloadframeworks_base-b7f3f92ac200fb22cd8d880b63a5c0ef2bad5354.zip
frameworks_base-b7f3f92ac200fb22cd8d880b63a5c0ef2bad5354.tar.gz
frameworks_base-b7f3f92ac200fb22cd8d880b63a5c0ef2bad5354.tar.bz2
Use the correct parent size to initialize animations
The original logic would use out-of-date parent sizes to initialize animations. If the screen size is changed after assigning mAnimDw and mAnimDh in the constructor of WindowStateAnimator, the fromDeltaY (in the most cases) of TranslateAnimation would be initialized incorrectly. In this change, we always use up-to-date parent sizes to initialize animations to prevent the issue. https://code.google.com/p/android/issues/detail?id=170348 Change-Id: Ib9c609121228934bdb463263feb1924eb389c1d2
Diffstat (limited to 'native')
0 files changed, 0 insertions, 0 deletions