Go to file
Jesse Hall 0de75f3f53 Stop using transparent region for computing visible regions (DO NOT MERGE)
The transparent region hint is computed only from view layout
locations, ignoring post-layout translation. If a SurfaceView is layed
out with no other views above it, but a view is moved above it
post-layout, that view's layout bounds would be subtracted from the
window's transparent region instead of its drawing bounds. Prior to
this change, the view would not be visible (except where its layout
bounds and drawing bounds overlap).

With this change, composition uses visible regions computed without
regard to the transparent regions. However, if all of a layer's
visible region is transparent, it will be removed from the list of
layers to composite. This doesn't fix the root problem of incorrect
transparent regions, and doesn't prevent bad composition in all cases.
But it does avoid it for some existing apps, while still allowing the
transparent region hint to save power in the important
fullscreen-video-in-a-SurfaceView case.

Change-Id: If2d929a10399b80401ef902abb232233a7f3d16d
2012-10-08 10:56:03 -07:00
build I am having second thoughts about 512m for the large heap size. 2012-06-08 13:02:09 -07:00
cmds Allow disable of dumpstate vibrate 2012-09-17 11:20:19 -05:00
data/etc Move com.nxp.mifare to frameworks/native. 2012-04-12 21:24:08 -07:00
include Forward compatibility patch. 2012-08-27 16:44:39 -07:00
libs Update tests for new build target 2012-10-02 09:42:49 -07:00
opengl Merge "Return back-end result from eglDestroyImageKHR" 2012-09-24 14:56:03 -07:00
services Stop using transparent region for computing visible regions (DO NOT MERGE) 2012-10-08 10:56:03 -07:00
MODULE_LICENSE_APACHE2
NOTICE