Thanks much for the tips. It does indeed seem a bit scattered.
On Oct 10, 1:19 pm, Mark Murphy <mmur...@commonsware.com> wrote: > Dan Sherman wrote: > > Slightly better answer than mine :) > > Heh, actually, I was thinking the reverse -- I keep forgetting about > Configuration. For things Configuration supports (e.g., keyboard), > that's a much better solution than looking at public fields on Build. > > At some point, we may need to create a DeviceCapabilities class, though, > that wraps Configuration and also reports back everything else > developers will want: location of the pointer (portrait? landscape? > both?), does it have a camera, etc. You can get answers for a lot of > those things from the API, but they're scattered. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > Looking for Android opportunities?http://wiki.andmob.org/hado --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
