| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Make sure to take into account the current matrix to calculate the right
global bounds
Tag operations with the matrix that affected their drawing
Change-Id: Iadda9f3849dc3df1507e63423ff8d3ad0f37d74e
|
|
|
|
| |
Change-Id: I1380ae53139d5f50a25ea5edb61ec8b6818112ca
|
|
|
|
| |
Change-Id: I967c8e2ea209c848e6a09b44390ab2228b213ca5
|
|
|
|
|
|
|
|
|
| |
Makes more sense to have PlatformGraphicsContextRecording
do the optimizations as it already has all of the interesting data
rather than have GraphicsOperationCollection "deep inspect" the
stream
Change-Id: I0dba6531a352d178afbee2c5eea7d67b82c28df5
|
|
|
|
| |
Change-Id: I086a3ff7b6191bf5e20f8b5f6f74bcc7d2e867c2
|
|
|
|
|
|
|
|
|
|
|
| |
Don't record state changes that didn't actually change state
Due to GraphicsContextAndroid::syncPlatformContext these 4 states
are set before every draw call. This is cheap for PlatformContextSkia,
as it detects that nothing has changed and so doesn't do anything. However,
PlatformGraphicsContextRecording would always record these same 4 commands
over and over again, which isn't efficient
Change-Id: I386bcb91c7851824ed01de1856ce6f6a358f8eb4
|
|
|
|
| |
Change-Id: Ifc514b1cfc12298c65a6c553c749a7b35520de7b
|
|
Change-Id: I41feadb23dce25af321331c459eb159c6141831b
|