On Sun, Jul 22, 2012 at 7:46 AM, RichardC <richard.crit...@googlemail.com> wrote: > How about View width and height instead of Display?
Precisely. It matters not a whit how big the display is. What matters is how big the preview SurfaceView can be, after taking everything else into account. >> So, correct me if I'm wrong, but that would seem to be at least one >> valid use. And in this case, it seems to be not only the right way, >> but THE way. The Camera AOSP app appears to use DisplayMetrics once, to determine the screen density. It does not use getHeight() and getWidth(). If it were THE way, the Camera app would be using it; otherwise the Camera app would not work. DisplayMetrics seems to be infrequently used overall in the AOSP apps, and even then is used primarily for density. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in NYC: 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
