W3bbo said:elmer said:*snip*
"Wont Fix" issues are the most annoying and frustrating to me: people have genuine issues with the software and dutifully report them, only to be told, with a smile, "No"; it reminds me too much of those unhelpful receptionists who decline any request without giving further information.
I'd certainly be a lot happier with the situation if they explained why they made that design choice; I certainly can't see any possible benefit, and if they're going to change something like this why not make it an option?
I don't know the VS extension API well enough, but might it be possible to write an extension to fix this?
I agree about won't fix being irritating, but it is a numbers game at the end of the day.
Microsoft themselves use the C++ editor to build visual studio and thousands of their own developers are not complaining. When you have worked on a large software application supporting many thousands of users, you learn to prioritise bug fixes and issues.
I bet you on connect there are loads more issues with loads more people complaining about, so rather than please 1 or 2 people, and annoy hundreds or thousands, a decision is taken against you, as in this case.
I have not used C++ for 5 years or so, but something tells me there is a fix available for this issue, either a setting or a registry hack.
Mind you, I installed Windows 7 and just used it, just like I installed Visual studio 2010 and just used it. People that stayed on XP and missed Vista have a lot more to learn abaout win 7, but to me Vista and windows 7 are very similar.
I think (I mean this in the nicest way) that you should "deal with it" as Dr Herbie would say.