Inefficient View alpha usage

平常在用systrace分析app性能的时候，经常有这样的警告：

Alpha是图形界面开发中常用的特效，通常我们会使用以下代码来实现Alpha特效：

view.setAlpha(0.5f);View.ALPHA.set(view, 0.5f);ObjectAnimator.ofFloat(view, "alpha", 0.5f).start();view.animate().alpha(0.5f).start();view.setAnimation(newAlphaAnimation(1.0f, 0.5f));

其效果都等同于：

canvas.saveLayer(l,r,t,b, 127,Canvas.CLIP_TO_LAYER_SAVE_FLAG);

所以常见的alpha特效是通过将图像绘制到offscreen buffer中然后显示出来，这样的操作是非常消耗资源的，甚至可能导致性能问题，在开发过程中我们可以通过其他方式避免创建offscreen buffer。

TextView

对于TextView我们通常需要文字透明效果，而不是View本身透明，所以，直接设置带有alpha值的TextColor是比较高效的方式。

// Not thistextView.setAlpha(alpha);

// 以下方式可以避免创建 offscreen buffer

intnewTextColor = (int) (0xFF* alpha) <<24| baseTextColor &0xFFFFFF;textView.setTextColor(newTextColor);

ImageView

同样的对于只具有src image的ImageView，直接调用setImageAlpha()方法更为合理。

// Not this, setAlpha方法由View继承而来，性能不佳imageView.setAlpha(0.5f);

// 使用以下方式时，ImageView会在绘制图片时单独为图片指定Alpha

// 可以避免创建 offScreenBuffer

imageView.setImageAlpha((int) alpha *255);

CustomView

类似的，自定义控件时，应该直接去设置paint的alpha。

// Not thiscustomView.setAlpha(alpha);// But thispaint.setAlpha((int) alpha *255);canvas.draw*(..., paint);

同时Android提供了hasOverlappingRendering()接口，通过重写该接口可以告知系统当前View是否存在内容重叠的情况，帮助系统优化绘制流程，原理是这样的：对于有重叠内容的View，系统简单粗暴的使用 offscreen buffer来协助处理。当告知系统该View无重叠内容时，系统会分别使用合适的alpha值绘制每一层。

/** * Returns whether this View has content which overlaps. This function, intended to be * overridden by specific View types, is an optimization when alpha is set on a view. If * rendering overlaps in a view with alpha < 1, that view is drawn to an offscreen buffer * and then composited it into place, which can be expensive. If the view has no overlapping * rendering, the view can draw each primitive with the appropriate alpha value directly. * An example of overlapping rendering is a TextView with a background image, such as a * Button. An example of non-overlapping rendering is a TextView with no background, or * an ImageView with only the foreground image. The default implementation returns true; * subclasses should override if they have cases which can be optimized. * *@returntrue if the content in this view might overlap, false otherwise. */publicbooleanhasOverlappingRendering(){returntrue;}