Linked by Thom Holwerda on Mon 11th Jun 2012 21:19 UTC
Permalink for comment 521790
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/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2006-07-04
In Windows 7, an app declares in its manifest whether its "DPI-aware" or not. If so, then W7 doesn't do anything to the app, since the app handles high DPI on its own (and when it's done right, it's very good).
But if an app doesn't declare itself to be DPI aware, then W7 uses XP DPI scaling for DPI between 100% and 125% (where 100% is 96 DPI), then above 125% W7 just does a bitmap scaling, which looks horrible (though its more "accurate" than what XP would do). This is the default behavior, but the user can change that behavior in the DPI Control Panel (that is, the user can change the threshold for XP DPI scaling, and I think a user can choose to always use XP behavior for non-DPI aware apps).
Note: I typed the above from memory; I don't vouch for it to be 100% accurate.
Windows 8 has a better high-DPI behavior, at least for Metro apps.