Linked by Thom Holwerda on Tue 23rd Oct 2012 19:12 UTC
Permalink for comment 539965
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
More News »
Sponsored Links



Member since:
2005-11-29
The XAML stack handles all of this easily.
By default the layout is adaptive, though you can opt-in to a fixed layout with a styled letterbox (Often even showing relevant content).
The only place where scaling by non whole multipliers is a problem is when using bitmapped content, which is why Microsoft has guidelines to where possible provide images at specific scales.
Even then, you can control the quality of the scaling of Bitmaps in the event that you don't control the scales that they're presented at (Remote images or something).
On top of that, you can tell the Layout engine to round its measurements and not put you on a sub-pixel boundary (Which causes fuzziness even with vector drawing) using UseLayoutRounding.
There's very simple rules developers should follow on Windows 8 and they'll be fine scaling to higher resolutions and differing aspect ratios.