[android-developers] Re: Supporting Galaxy Note Issues Due To It Displaying Itself as a LARGE screen layout.

Hmmm I just realized that the Samsung Galaxy Tab 7.0" Plus was
released with 3.2 so we can use the -sw qualifier - initially I was
thinking "great we gotta do the qualifier dance around the 7.0" Plus"
because the Samsung Galaxy Tab 10.1" I have is still stuck on 3.1 and
I thus assumed all Samsung Honeycomb tablets would be at 3.1.

I had access to one of those knockoff 800x480 7" Android 2.2 tablets
(but it is not with me anymore). I don't remember if it acted like the
mdpi device that it should.

On Feb 8, 8:33 am, Dianne Hackborn <hack...@android.com> wrote:
> On Sun, Feb 5, 2012 at 5:42 AM, albnok <alb...@gmail.com> wrote:
> > Er... since when could we do that? As far as I know the exact
> > qualifiers only came about in Android 3.2.
>
> > layout-large-port-xhdpi-1280x800
>
> > I am thinking layout-large-port-xhdpi would make sense, though.
>
> You should never, ever see a resource qualifier like that.  That is,
> frankly, insane.
>
> Also mixing density with screen size almost certainly means you are doing
> something on.  I can guarantee that you that there will be device
> configurations in the future that break with such things, because density
> has *nothing* to do with screen size.
>
> The first this is please, please read the documentation and my blog post
> here:http://android-developers.blogspot.com/2011/07/new-tools-for-managing...
>
> The blog post includes examples of how to use the new selectors in a
> compatible way with older devices.
>
> Also, yes, the large size bucket is problematic, as the blog post
> discusses.  There isn't anything we can do to help this for older versions
> of the platform. My suggestion if you need to deal with this is to just
> fall back on doing it programmatically -- define two layouts that are not
> qualified by screen size, and when your code runs look at the actual screen
> size (converted to dp units) and pick the one to use based on that.
>
> Or alternatively, just forget about large, code against xlarge and the new
> -sw qualifier, and make sure your normal layout resizes reasonably when
> running on a larger screen.
>
> --
> Dianne Hackborn
> Android framework engineer
> hack...@android.com
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en