GP 2016 has the same behavior that GP 2013 and GP 2015 do in that the window sizes do not scale with DPI. I have a Surface Pro 3 that ships with DPI at 150% and resolution is 2160x1440. This is the same kind of configuration you would see with a monitor that has a very resolution with DPI configured to inflate window sizes. What's very odd about all of this is that while GP 2013, 2015, and 2016 do not recognize and inflate their window sizes with DPI, GP 2010 does. I ended up turning DPI "off" (100%) and using the Nvidia display drivers to create a custom 1440x960 (maintaining 1.5 aspect ratio). This "fixes" applications like GP and others that do not recognize DPI and scale with the setting. 1440x960 at 100% DPI is the same effective resolution as 2160x1440 at 150% DPI (2160/1.5=1440 and 1440/1.5=960). You lose some visual clarify/fidelity to be sure but not as much as I thought and I'm perfectly happy with the Surface Pro 3 at 1440x960 at DPI at 100%. It's at least the lesser of 2 evils for me. The other very annoying application that has this issue is RDP when RDPing into a server that is Windows Server 2008 or lower. It doesn't seem like there's enough broad support for DPI for it to be used as a "solution" for inflating the window sizes for large resolution monitors.
↧
