Go to file
Mathias Agopian 0cd545f142 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
2012-06-07 17:12:20 -07:00
build Add new Dalvik memory limit definition. 2012-06-05 18:23:11 -07:00
cmds Dump packages.xml as root. 2012-05-17 13:03:34 -07:00
data/etc Move com.nxp.mifare to frameworks/native. 2012-04-12 21:24:08 -07:00
include Merge "Support looper callbacks based on smart pointers." into jb-dev 2012-05-31 18:39:13 -07:00
libs Merge "Support looper callbacks based on smart pointers." into jb-dev 2012-05-31 18:39:13 -07:00
opengl Implement the EGL_KHR_fence_sync in libagl 2012-05-22 12:11:41 -07:00
services sometimes we would incorrectly scale the content of a surface 2012-06-07 17:12:20 -07:00
MODULE_LICENSE_APACHE2
NOTICE