One other interesting thing .... My FWQVGA avd (android 2.1 + skin WQVGA432) seems to work only for one session. If I close and run it again the resolution changes, icons appear a lot bigger and it displays the UI componentes totally misplaced. I don´t know if I made a huge mess with last posts so I will try to resume my main concern:
If I set android:largeScreens="false" so android can adapt my layout for large screens, my /layout-normal-long isn´t displayed correctly on my FWQVGA avd (android 2.1 + skin WQVGA432). If I set android:largeScreens="true" the layout is displayed perfectly on the same AVD (need to recreate it because, as I said, just work for 1 session) but is not adjusted for large devices. Well, took a long time to figure this out because to me it makes no sense since this FWQVGA avd emulates a normal device with a low density, so no changes to android:largeScreens should have impact to it, right? On 30 abr, 02:03, Gabriel Simões <[email protected]> wrote: > Some other conclusions ... > > I´ve have found another interesting fact (at least on my environment): > > if on my AndroidManifest.xml I set android:largeScreens="true", my avd > running the skin WQVGA432 works just as it is supposed to (there > shouldn´t be any connection between them, right?), but large avds > display my layout horribly (as expected). > Well, if I set it as false, don´t ask me why the layout is not > displayed right on WQVGA432. Indeed it looks like it´s height is a lot > smaller than it should (I have an widget anchored at the bottom of the > screen and it shows up +/- at 2/3). The only thing I did was to change > this setting, back and forth, many times and the error appeared > repeatedly in all of them. > Leaving this way my app should now work on cellphones but not on > tablets or other devices (since it´s gonna look back on a FQWVGA > phone.). > Any thoughts on this one? > > Gabriel > > On 29 abr, 23:48, Gabriel Simões <[email protected]> wrote: > > > > > > > Thanks for your reply Mark! > > Took some time to answer because I was testing the new layouts. > > What I did: > > > /layout (for HVGA displays - medium density and normal size) > > /layout-small (for QVGA displays - low density and low size) > > /layout-long (for all the other displays). > > > At first everything was working great! indeed better than I expected. > > Well, I wrote "was" because I only tested on emulators of small > > (QVGA) > > and medium size (WQVGA, FWQVGA, HVGA, WVGA, FWVGA) displays. > > When I tried to use /layout-long on emulators of large displays > > (skins > > WVGA800 and WVGA854 with density = 160 - medium) all my widgets were > > displayed just like in the HVGA emulator (I guess as expected since > > they have the same density) but, as the screen is much bigger, they > > were completly misplaced. > > > By what I understand, large displays are only for tablets ? Motorola > > Droid and Google Nexus One are both Normal Size High Density display > > devices, am I right? > > > Thinking so I decided to change AndroidManifest.xml to use > > compatibility mode for large screens. Problem 2: the display was not > > right because it was loading a long layout and rescaling it for > > compatibility as a normal layout (this, to me, is a bug). > > > Then, to finish the "saga" I decided to rename the folder /layout-long > > to /layout-normal-long (so it works only for cellphones). Now, for > > large displays, the compatibility mode works nice (using my HVGA > > layout, unfortunately), and for normal and small displays everything > > seems ok. > > > I just don´t know if it was the best solution. > > > Thanks, > > Gabriel Simões > > > On 28 abr, 13:16, Mark Murphy <[email protected]> wrote: > > > > Gabriel Simões wrote: > > > > If I´m allowed to make another question ... > > > > > Any ideas on how I could handle the different screen height/width > > > > proportions (for example, the WVGA´s proportion is bigger than the HVGA > > > > ´s so a layout based on relativeLayout build up considering a HVGA > > > > device will leave a lot of empty space in the bottom of a WVGA > > > > device). That´s my main problem right now and to fix this I can only > > > > think about creating a new layout for large/normal-hpdi devices, one > > > > for normal-ldpi (if the one for the large screens doesn´t work here, > > > > but I think this should work) and a last one for small-ldpi devices. > > > > There are the -long and -notlong resource set suffixes you can use to > > > distinguish between these aspect ratios. > > > > -- > > > Mark Murphy (a Commons > > > Guy)http://commonsware.com|http://twitter.com/commonsguy > > > > Android Development Wiki:http://wiki.andmob.org > > > > -- > > > 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 > > > athttp://groups.google.com/group/android-developers?hl=en > > > -- > > 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 > > athttp://groups.google.com/group/android-developers?hl=en-Ocultar texto das > > mensagens anteriores - > > > - Mostrar texto das mensagens anteriores - > > -- > 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 > athttp://groups.google.com/group/android-developers?hl=en- Ocultar texto das > mensagens anteriores - > > - Mostrar texto das mensagens anteriores - -- 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
