summaryrefslogtreecommitdiffstats
path: root/build
diff options
context:
space:
mode:
authorMathias Agopian <mathias@google.com>2012-06-07 14:18:55 -0700
committerMathias Agopian <mathias@google.com>2012-06-07 17:12:20 -0700
commit0cd545f14261d829513e0d6e8fa5e4e4f3372b3d (patch)
treef215784f7b8e7031dfba053cc790da94751434de /build
parentba43e0a1faee9629ca2d0beb53dd6c44bb9bfd05 (diff)
downloadframeworks_native-0cd545f14261d829513e0d6e8fa5e4e4f3372b3d.zip
frameworks_native-0cd545f14261d829513e0d6e8fa5e4e4f3372b3d.tar.gz
frameworks_native-0cd545f14261d829513e0d6e8fa5e4e4f3372b3d.tar.bz2
sometimes we would incorrectly scale the content of a surface
this would happen when a resize was pending (ie: we have received and processed a resize transaction but have not received a buffer with the right size) and a new transaction came in that didn't involve a resize, for instance a translate-only transaction. in this case, we would incorrectly update the drawing state with the pending size, eventhough we still don't have a buffer for it. the solution is quite simple, we never allow the size to propagate from current to drawing state during the regular transaction processing (unless we are in fixed-size mode -- meaning we don't need to have a matching size buffer), this propagation happens later once we receive the buffer. Bug: 6624163 Change-Id: I11a97e4b88a7f3a0571ddcfe99c86cb04ce01a4d
Diffstat (limited to 'build')
0 files changed, 0 insertions, 0 deletions