Cache blur mask for rects which can not break into nine-patch

src/core/SkMaskCache.h

 /*
  * Copyright 2014 Google Inc.
  *
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file.
  */
 
 #ifndef SkMaskCache_DEFINED
 #define SkMaskCache_DEFINED
 
@@ skipping 21 matching lines @@
 
     /**
      * Add a mask and its pixel-data to the cache.
      */
     static void Add(SkScalar sigma, SkBlurStyle style, SkBlurQuality quality,
                     const SkRRect& rrect, const SkMask& mask, SkCachedData* data,
                     SkResourceCache* localCache = NULL);
     static void Add(SkScalar sigma, SkBlurStyle style, SkBlurQuality quality,
                     const SkRect rects[], int count, const SkMask& mask, SkCachedData* data,
                     SkResourceCache* localCache = NULL);
+

[reed1, 2014/12/22 21:38:15]

Why do these take their parameters in a slightly different order from FindAndRef
/ Add?

Can we name them some way to reflect how they are different from FindAndRef /
Add?
e.g. FindAndCopy?

Either way, I think we need some dox to describe what these do, esp. how they
are different.

[qiankun, 2014/12/23 10:54:32]

Modify the name and re-order parameters for FindAndCopy/AddAndCopy API. Add some
comments to point the difference with FindAndRef/Add. 

+    static bool FindCachedRRect(SkMask* mask, SkScalar sigma, SkBlurStyle style,
+                                SkBlurQuality quality, const SkRRect& rrect);
+    static void AddCachedRRect(const SkMask& mask, SkScalar sigma, SkBlurStyle style,
+                               SkBlurQuality quality, const SkRRect& rrect);
+    static bool FindCachedRects(SkMask* mask, SkScalar sigma, SkBlurStyle style,
+                                SkBlurQuality quality, const SkRect rects[], int count);
+    static void AddCachedRects(const SkMask& mask, SkScalar sigma, SkBlurStyle style,
+                               SkBlurQuality quality, const SkRect rects[], int count);
 };
 
 #endif