问题描述
为什么没有图形加速蜂窝中默认开启？是否有任何情况下，当它的最好禁用它？
Why isn't graphics acceleration turned on by default in Honeycomb? Are there any situations when it's better to leave it disabled?
推荐答案
这不是默认的兼容性原因开启。接通电源时（尽管缺少的部分非常少，很少使用），并有可能在新的实施错误画布API的不是100％的支持。也有新的约束条件（例如，如果你尝试绘制比最大的OpenGL纹理尺寸的位图，它就会失败。）
It is not turned on by default for compatibility reasons. Not 100% of the Canvas API is supported when turned on (although the missing parts are very few and rarely used) and there might be bugs in the new implementation. There are also new constraints (for instance if you try to draw a bitmap larger than the maximum OpenGL texture size, it will fail.)
新的渲染管线还采用了原生的显示列表每个视图，从而触发虫子在某些应用程序。例如，如果一个视图依赖于其父无效（）重绘自身，它在应用程序中的错误，但它作品没有硬件加速。它将然而，并非硬件加速上工作。
The new rendering pipeline also uses native display lists for each View, which triggers bugs in some apps. For instance, if a View relies on its parent to invalidate() to redraw itself, it's a bug in the app, but it "works" without hardware acceleration. It will however not work with hardware acceleration on.
我们的目标是在默认情况下尽快使硬件加速，但我们并不想打破的应用程序。也就是说，应用程序使用标准的意见和API应该只是罚款。
Our goal is to make hardware acceleration on by default as soon as possible but we do not want to break apps. That said, apps using standard views and APIs should work just fine.
这篇关于为什么没有图形加速蜂窝中默认开启？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！