diff options
author | 2014-06-09 06:25:34 -0700 | |
---|---|---|
committer | 2014-06-09 06:25:34 -0700 | |
commit | 9f1c241e0d8a756fca1ec2dacb565eec83166d5f (patch) | |
tree | 77a588bd485fb27de5d4dc81a78624968361f65e /gm | |
parent | 5713352a64936428d37a721382d021f4a9002172 (diff) |
Remove SkPicture::kUsePathBoundsForClip_RecordingFlag
The real question is whether we ever want to record a picture without using the path bounds for a conservative (but faster) clip answer?
R=reed@google.com, mtklein@google.com, djsollen@google.com, scroggo@google.com
Author: robertphillips@google.com
Review URL: https://codereview.chromium.org/316143003
Diffstat (limited to 'gm')
-rw-r--r-- | gm/gmmain.cpp | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/gm/gmmain.cpp b/gm/gmmain.cpp index 6d3f619b98..37237695c0 100644 --- a/gm/gmmain.cpp +++ b/gm/gmmain.cpp @@ -1669,8 +1669,7 @@ ErrorCombination run_multiple_modes(GMMain &gmmain, GM *gm, const ConfigData &co // result that can be validated against comparisonBitmap. SkScalar recordScale = SkScalarInvert(replayScale); SkPicture* pict = gmmain.generate_new_picture( - gm, kTileGrid_BbhType, SkPicture::kUsePathBoundsForClip_RecordingFlag, - recordScale); + gm, kTileGrid_BbhType, 0, recordScale); SkAutoUnref aur(pict); SkBitmap bitmap; // We cannot yet pass 'true' to generate_image_from_picture to |