Fix two SkRecord-backed layer hoisting bugs

The two bugs are/were:
The old loop to draw the hoisted layers included the saveLayer call which caused double application of the layer's paint (This is the +1 change).

The hoisted layer is intended to be drawn in device coordinates. The old code was drawing it in the coordinate space of the saveLayer thus it was misplaced (This is the setMatrix change).

R=bsalomon@google.com

Author: robertphillips@google.com

Review URL: https://codereview.chromium.org/551843002

1 files changed, 2 insertions, 2 deletions

diff --git a/src/gpu/GrLayerHoister.cpp b/src/gpu/GrLayerHoister.cpp
index ac09df825b..49ca338bb2 100644
--- a/src/gpu/GrLayerHoister.cpp
+++ b/src/gpu/GrLayerHoister.cpp
@@ -95,7 +95,7 @@ void GrLayerHoister::DrawLayers(const SkPicture* picture,
             atlasCanvas->concat(layer->ctm());
 
             SkRecordPartialDraw(*picture->fRecord.get(), atlasCanvas, bound,
-                                layer->start(), layer->stop());
+                                layer->start()+1, layer->stop());
 
             atlasCanvas->restore();
         }
@@ -129,7 +129,7 @@ void GrLayerHoister::DrawLayers(const SkPicture* picture,
         layerCanvas->concat(layer->ctm());
 
         SkRecordPartialDraw(*picture->fRecord.get(), layerCanvas, bound,
-                            layer->start(), layer->stop());
+                            layer->start()+1, layer->stop());
 
         layerCanvas->flush();
     }