> 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.
Correct me if I am wrong, but when you set eg. applicationDPI=120 in the Application, only the css @media 120 is considered, same for actionScript applicaitonDPI tests, and global scaling is applied to the application (through stage.transform), which means you will get fractional padding and border widths anyway. 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
