
"Though Windows 7 doesn't quite have the same experience when it comes to resolution and scaling control as OS X does - it can be a bit of a chore to get it just the way you like it - it's still quite useable on the Retina MacBook Pro's 15" 2880 x 1800 pixel screen. I recommend running Windows at full resolution with the 150 percent scaling setting - that seemed to give the best overall usability. 'Retina' class desktop displays are still a relative rarity today, so it will be some time before software developers adapt applications to best take advantage of such a resolution. In the meantime,
you should have no trouble running Windows on the Retina MacBook Pro if the need arises." A look at how Windows 8 handles the display would've been nice, too.
Member since:
2006-07-04
Microsoft changed that starting with Windows 7. SetProcessDPIAware is deprecated and not recommended; instead, DPI-aware apps are to declare themselves as such in their manifest. One can hard-code DPI=true XML code into their manifest, or, starting with VS2010, devs can check the "DPI-Aware" checkbox in the manifest panel. [/q]
I think the problem here might be that (pre-Metro, at least) Microsoft's "high DPI" SDK documentation focuses on 150% DPI. The Windows 7 SDK documentation says, "The standard DPI settings are 100% (96 DPI), 125% (120 DPI), and 150% (144 DPI). The user can also apply a custom setting. Starting in Windows 7, DPI is a per-user setting.", so developers of DPI-aware apps target those DPI settings (adjusting their code and providing graphical resources (like icons) for each of those DPI settings). But Retina display is 200% DPI, so lots of DPI-Aware Windows apps wouldn't handle that in optimal fashion.