Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual Studio 2010 looks "zoomed in"
    primarykey
    data
    text
    <p>Today, I installed Visual Studio 2010 Professional on a new laptop with a fresh Windows 7 Ultimate 64-bit install. I, being quite used to the look of Visual Studio 2010, instantly spotted that something was wrong. It seems that the Visual Studio application is "zoomed in", in a way. The text is much larger (even though it says that the zoom level is 100%, and the text size is 10, which is the same as what I used before), and generally, so are the other windows like the Solution Explorer and Output console. The quality of the icons and images is also very bad.</p> <p>Here are two comparison images (I wasn't allowed to post images, so some links will have to do):</p> <p>This is the look that I'm used to. I see plenty of text in the windows, and the icons are fine.</p> <p><a href="http://i51.tinypic.com/2mq8dau.png" rel="nofollow">http://i51.tinypic.com/2mq8dau.png</a></p> <p>This is what greeted me when I installed VS2010 on my new laptop. The icons look stretched, and I can fit a lot less code in the window.</p> <p><a href="http://i56.tinypic.com/35k0fo4.png" rel="nofollow">http://i56.tinypic.com/35k0fo4.png</a></p> <p>The screen resolution on my old computer is 1920x1200 and the resolution on my new computer is 1920x1080. (I resized the VS window on my old computer to about 1920x1080 to show the difference). </p> <p>It looks like my image host resized the images as well, but you should still be able to see the difference.</p> <p>Has anyone had the same problem? I'm hoping it's just some visual settings. If anything is missing, I will be happy to provide more information.</p> <p>Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload