| /frameworks/base/docs/html/guide/topics/graphics/ |
| hardware-accel.jd | 625 <dt><strong>Don't modify bitmaps too often</strong></dt>
|
| /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6/sysroot/usr/include/X11/ |
| Xlibint.h | 87 int bitmap_pad; /* padding requirements on bitmaps */
[all...] |
| /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8/sysroot/usr/include/X11/ |
| Xlibint.h | 87 int bitmap_pad; /* padding requirements on bitmaps */
[all...] |
| /external/chromium_org/content/browser/web_contents/ |
| web_contents_impl.cc | [all...] |
| web_contents_impl.h | [all...] |
| /external/chromium_org/third_party/mesa/src/docs/ |
| VERSIONS | 54 - fixed "flickering bitmaps" in double buffer mode
174 - fixed bug when blending lines, points, bitmaps outside of window
672 - glXUseXFont() bitmaps were vertically shifted by one pixel
[all...] |
| /external/mesa3d/docs/ |
| VERSIONS | 54 - fixed "flickering bitmaps" in double buffer mode
174 - fixed bug when blending lines, points, bitmaps outside of window
672 - glXUseXFont() bitmaps were vertically shifted by one pixel
[all...] |
| /external/e2fsprogs/po/ |
| cs.po | [all...] |
| es.po | [all...] |
| nl.po | [all...] |
| tr.po | [all...] |
| ca.po | [all...] |
| pl.po | [all...] |
| sv.po | [all...] |
| vi.po | [all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_beta/cpp/ |
| classpp_1_1_graphics2_d.html | 316 <p>In the case of an animation, you will want to allocate a new image for the next frame. It is best if you wait until the flush callback has executed before allocating this bitmap. This gives the browser the option of caching the previous backing store and handing it back to you (assuming the sizes match). In the optimal case, this means no bitmaps are allocated during the animation, and the backing store and "front buffer" (which the module is painting into) are just being swapped back and forth.</p>
[all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_dev/cpp/ |
| classpp_1_1_graphics2_d.html | 316 <p>In the case of an animation, you will want to allocate a new image for the next frame. It is best if you wait until the flush callback has executed before allocating this bitmap. This gives the browser the option of caching the previous backing store and handing it back to you (assuming the sizes match). In the optimal case, this means no bitmaps are allocated during the animation, and the backing store and "front buffer" (which the module is painting into) are just being swapped back and forth.</p>
[all...] |
| /external/chromium_org/native_client_sdk/doc_generated/pepper_stable/cpp/ |
| classpp_1_1_graphics2_d.html | 316 <p>In the case of an animation, you will want to allocate a new image for the next frame. It is best if you wait until the flush callback has executed before allocating this bitmap. This gives the browser the option of caching the previous backing store and handing it back to you (assuming the sizes match). In the optimal case, this means no bitmaps are allocated during the animation, and the backing store and "front buffer" (which the module is painting into) are just being swapped back and forth.</p>
[all...] |
| /external/chromium_org/third_party/skia/src/core/ |
| SkBitmap.cpp | 1056 // Currently supported only by texture-backed bitmaps.
[all...] |
| /external/e2fsprogs/lib/ext2fs/ |
| ext2fs.h | 738 /* bitmaps.c */
[all...] |
| /external/e2fsprogs/misc/ |
| e2image.c | [all...] |
| /external/opencv/cxcore/include/ |
| cxtypes.h | 378 1 - bottom-left origin (Windows bitmaps style). */
[all...] |
| /frameworks/base/core/java/android/widget/ |
| ImageView.java | 540 // if this is used frequently, may handle bitmaps explicitly
[all...] |
| RemoteViewsAdapter.java | 664 // Calculate the memory usage of all the RemoteViews bitmaps being cached
[all...] |
| /frameworks/base/docs/html/about/versions/ |
| android-3.1.jd | 528 <li>Helpers for managing bitmaps
[all...] |
