On Sat, Jul 7, 2012 at 3:33 PM, Jim Graham <[email protected]> wrote: > No, but it's my alternative for blending any photographic color filters > (e.g., solid color, graduated, and/or split-field) with the photo, and > then doing stuff like brightness, ontrast, color balance, gamma, and so > on, without running into an OOM error. It's that, or limit the image > size, which I really hate the idea of forcing users with higher > resolution cameras to do, even if only one step down in resolution. It > just doesn't seem right, IMHO.
Off the cuff... Step #1: Use ActivityManager and getMemoryClass() to determine how big your heap size is. Step #2: Ask the Camera getSupportedPictureSizes(). Step #3: Choose a picture size based upon the memory class and needs of your app. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in DC: http://marakana.com/training/android/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
