Add high resolution icons for those who use high DPI screens
When you set your screen to high DPI (>100%) icons in toolbars get really blurry. In VS 2010 it was a pain to create great UI while your ide looked so bad.
Icons should look pixel perfect independently of your DPI.
Miguel Hurtado
shared this idea
3 comments
-
Thomas Darling
commented
Absolutely agree. Visual Studio must support high DPI screens correctly.
Please do proper layout testing at the standard 125%, 150% and 200% DPI settings, and include graphic assets specifically designed for those scales. Currently, all my icons look like a gray, blurry mess at 150%, and that is just plain unacceptable. You already have the icon designs, so redrawing them at more resolutions should be an easy task - ****, I will do it for you for free, if that is what it takes.
Looking at code all day, we are probably among those users who can benefit the most from the clear text and extra workspace provided by a high DPI screen, so supporting it should be an absolute requirement.
-
Cornan
commented
I believe this is the same as requesting the return of "large icons" in the Visual Studio toolbars.
VS2008 still had the option, and some programs still offer THREE icon sizes, and different icon sizes for different toolbars in the same program.
For those of us past 50 with less than perfect eyesight, the tiny icons of VS2010 and now the tiny MONOCHROME icons of VS2012 are a total pain.
-
Marc
commented
What a shame that VS2012 is released without medium- or large-font-supoort. VS2010 did this really well so its a basic functionality lost with VS2012. for people like me who's eyes are not the best (accessibility is the topic) this is a pain. We need medium- or large-font support but this is where things get fuzzy and are hardly recognizable. If that's not enough the icons are monochrome so we loose also the help that colors provide to recognize things faster and easier. What a pity. Did anybody do usability-tests/-design and QA on this product? What was the default screen-size MS used when developing? 20"? Nobody found this issue before the release?
