On Wed, Oct 30, 2013 at 3:41 PM, Maurice Amsellem <
maurice.amsel...@systar.com> wrote:

> There is still something that I don't get:
>
> According to my tests, flex navigation bar is now roughly 0.27'  high on
> all devices with SDK 4.11
> and it was 0.34' with SDK 4.10 on iPad 2, and 0.27 on all other devices.
>
> So now people complain that it's too small on iPad.
>
> So why didn't they complain that it WAS too small on other devices with
> SDK 4.10?
>
>
As you mentioned, I think it is a very subjective thing :-)

Om


> Maurice
>
> -----Message d'origine-----
> De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
> Envoyé : mercredi 30 octobre 2013 23:36
> À : dev@flex.apache.org
> Objet : RE: Issue with mobile UI default sizes
>
> > It's easy enough for a user to change by  setting the application's
> > runtimeDPIProvider property change the boundary that 120 kicks in at
> > change classifyDPI to have a special case for iPad 1+2's
>
> Do you mean that would give 160 DPI for iPad 1+2 instead of 120.
>
> In this case, we fall back into the old issue that iPad 3 gets 240  DPI
> and iPad 1+2 get 160 DPI (  240 != 160 * 2), which was previously hacked by
> having iPad 3 DPI arbitrarily set to 320 DPI, using custom
> runtimeDPIProvider, which is very far to its actual 263 DPI.
>
> That's why I found in the first place that giving 120 DPI to iPad 1+2 and
> 240 DPI to iPad 3+4 was a good decision.
>
> So you will need to change iPad 3 to 320 as well...
>
> Maurice
>
> -----Message d'origine-----
> De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : mercredi 30
> octobre 2013 23:19 À : dev@flex.apache.org Objet : Re: Issue with mobile
> UI default sizes
>
> Hi,
>
> > I think it would be too disruptive to change it now.  Perhaps we could
> > document a way to modify it for folks who want more control?  What are
> > our options?
>
> I see 3 options:
> - It's easy enough for a user to change by  setting the application's
> runtimeDPIProvider property
> - change the boundary that 120 kicks in at
> - change classifyDPI to have a special case for iPad 1+2's
>
> Does anyone know what the proportion of 1+2 iPads vs 2-4 iPads out there?
>
> > On the other hand, as I am working on the new Android 4.x skins
> And I've not forgotten about that either.
>
> > I am thinking of having just one set of FXG files for all DPIs and
> > just scaling everything as required.
> May not work that well when it comes to borders width and control padding,
> looking through the old skins  the borders changed non proportionally to
> dpi.
>
> Justin
>

Reply via email to