Visual Studio 2010 Beta 1 | The Coffeehouse

Sven Groot
My name has 9 letters. Coincidence? I think not...

No need to hack the manifest, you can disable DPI scaling in the compatibility tab on the app's properties. And that does actually work fine with VS2008.

Maddus Mattus
Do, or do not. There is no try. - Yoda

I have the same issue, with the blurring text.

Scrolling seems to make it a lot worse!

Really hurts my eyes!

KevinB

In reply to Maddus Mattus

#May 20th @ 2:47 AM

Can't say I have noticed it, VS2010 looks very nice on my Dell 17" Laptop screen.

What is annoying me about VS2010 at the minute is a slight regression in the editor.

I normally open statement blocks and immediately close them. E.g.

for (....)

{

}

I then immediately press the up arrow to move above the closing brace and begin typing the actual code. In VS < 2010, this worked well and the up arrow moved the text position to nicely indented so I could begin coding. Now it moves it to the very left of the editor, so I need to manually tab the whole way across.

This is a minor issue I know, but it is pretty annoying when I have gotten so used to doing something a particular way.

stevo_
Human after all

In reply to KevinB

#May 20th @ 7:16 AM

Hmm, I haven't tried it yet but that would really frustrate me as I do the same.. I guess if it sticks I'll just have to learn not to try and close the scope first.

BitFlipper

In reply to littleguru

#May 19th @ 2:29 PM

I think your problem is that your cleartype is not calibrated properly. LCD screens differ in their RGB pixel layout, where some are clustered in a small triangle, and others are laid out in a straight line, with some in an RGB pattern, others in GBR, etc. So it is critical that your cleartype uses the correct settings. Go here to tune it:

http://www.microsoft.com/typography/ClearType/tuner/tune.aspx

Let us know if that helps.

littleguru
<3 Seattle

In reply to BitFlipper

#May 20th @ 8:34 AM

Did that already. The Windows (even Windows 7) ClearType is perfectly fine. I have only problems with the WPF one.

Ion Todirel
buuu

In reply to KevinB

#May 20th @ 7:16 AM

Hi

I'm in the project and build team, thanks for reporting that, I will submit a bug for the editor guys.

Thanks everyone for reporting.

@littleguru, we know about the font smoothness, we are working on that.

-Ion

KevinB

In reply to Ion Todirel

#May 20th @ 1:10 PM

I also noticed another (very minor) bug that I posted on Connect. I am sure ou guys are aware of it and it will be picked up in the final branding review but just to make a note of it:

The user settings folder where projects, snippets, settings etc. are stored is called 'Visual Studio 10' in Beta 1, presumably because this is what it was in the CTP and alpha.

Should this folder should be called 'Visual Studio 2010' in line with product branding and previous version releases?

Ion Todirel
buuu

In reply to KevinB

#May 20th @ 4:04 PM

of course, yes, that's temporarily I think

stevo_
Human after all

In reply to Ion Todirel

#May 20th @ 1:10 PM

Does this if you press up into a space, say if I write:

var x = 10;

var y = 20;

Imagine my cursor is sat after the 20; I hit up and rather than my cursor being sat under the 'v' of the first var, its sat right to the left.

Also, when you press ctrl+ . to bring up options (say to include a types namespace), the first option isn't auto selected like it is in vs2008.. which is frustrating.

exoteric
I : Next<I>

In reply to AndyC

#May 19th @ 4:17 PM

The whole point of font anti-aliasing though, is to compensate for a pixel-density deficit. At some point in time we may not even need ClearType anymore, well fingers crossed.

brian.shapiro
things go on as always

In reply to exoteric

#May 24th @ 1:21 AM

First we need a vector based UI

androidi

In reply to brian.shapiro

#May 24th @ 8:56 AM

Not really, the program could be lied to that the resolution is x*y and scaled 2x when the actual resolution is for example 2x*2y and the font rendering would actually utilize the extra real pixels.

This WPF text is pretty fuzzy and various ClearType settings don't really help on a CRT. No matter what, side by side vs2008 without CT is much sharper.

figuerres
???

In reply to brian.shapiro

#May 24th @ 8:56 AM

well more than half the time we have the tools to do things that way but we also need to get the coders to work in non-pixel mode.

i see all kinds of cases where relative / dynamic locations and sizes can be used but folks use pixels.
take web pages as a prime example you can markup with precentage, points, em's inches, millimiters and whatever else is in html and css but look how often folks use pixels.

stevo_
Human after all

In reply to figuerres

#May 24th @ 1:06 PM

Generally pixels are used because they 'just work' and have a much more simplistic model to ems for example.. browsers are capable enough today to mostly work around that 'flaw'.

W3bbo
The Master of Baiters

In reply to exoteric

#May 24th @ 1:21 AM

I disagree there. Even with 192dpi displays type still looks a lot better with subpixel antialiasing.

androidi: this reminds me of when WMP10 came out, it forced the use of Cleartype in the UI, even when system settings explicitly had it disabled.

AndyC

In reply to exoteric

#May 24th @ 1:21 AM

When we have 600dpi displays, you might have a point. Right now though a high dpi display + cleartype makes a massive difference. Getting away from 96dpi displays would do us a world of good, it just really needs software developers to start making it easier for us to move down that route.

W3bbo
The Master of Baiters

In reply to AndyC

#May 24th @ 4:09 PM

It's not software developers halting us (since you can 2x scale a 96dpi program for a 192dpi display without any issues) but the cost of manufacturing panels with that high a resolution. A good 24" 96dpi panel is still at least £400, and large-scale OLED displays are only a few years away.

vesuvius
Das Glasperlenspiel

In reply to W3bbo

#May 24th @ 4:41 PM

You guys are correct about the text being blurred in beta 1, that will be forthcoming in VS2010 beta 2 as the new WPF graphics and text clarity is scheduled to be added in that release.

This is not a bug or a fault, it's just what has been scheduled...Kevin Gjerstad, the WPF GPM

stevo_
Human after all

I think there are some quirks with how the text editor works for code, seemingly minor things will frustrate some developers.. I noticed one the other day but I failed to remember the steps.. but basically I was typing something and intellisense was displaying and I hit a key that I would expect to ignore the intellisense suggestion and leave it as I typed.. however intellisense still selected the first option.

Another thing that tripped me up was how the code tabs are now correct, in 08 the cross to close a tab would always be in the same detached place.. in 2010 you've fixed that up- which is great.. but its thrown me a couple of times Tongue Out

BitFlipper

So after installing VS 2010 Beta 1 myself, I have to admit the blurry text is horrible. If you scroll a list that contains text, some of the text goes blurry, then after you stop scrolling, it slowly "fades" back into focus. Quite a nauseating effect. I really can't see myself staring at VS for 8+ hours a day the way it is now.

I logged a bug, even though there are already similar bugs logged, just to make sure this problem is not swept under the rug. But thanks to vesuvious's reply, it looks like this will be taken care of.

The other thing I noticed is that the whole IDE feels like a step backwards, in the sense that it feels like some sort of cheesy web app. Very clunky. Hopefully this is also due to it being an early beta and that things will get polished so that it at least doesn't feel like such a step backwards.