On Wed, Oct 30, 2013 at 3:19 PM, Justin Mclean <jus...@classsoftware.com>wrote:
> 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. > > >From what I have seen, the borders are drawn programatically in ActionScript and the padding is set in CSS and applied in ActionScript. We can continue to do that. The FXG specifies only Rects, Paths and gradients. All of them have scale-9 settings, so they will scale properly regardless of size. Om > Justin
