Change All CAPS Menu in VS 2012 to VS Beta format File Edit Instead of FILE EDIT
Change All CAPS Menu in VS RC to VS Beta format File Edit Instead of FILE EDIT. Ref (http://blogs.msdn.com/b/visualstudio/archive/2012/05/08/visual-studio-11-user-interface-updates-coming-in-rc.aspx )
Who wants to be shouted at? Nobody. Please stop the obsession with making UI elements all caps. It serves no purpose but to waste space, annoy and remove attention away from the most important element in the IDE, the code.
David W Parvin commented
you can use this to fix your menus if you really need it:
Phil Murray commented
Caps lock does not. The default look and feel certainly does. Also, please understand that most of these UI topics were created for the Beta and while things are improving they are not yet fixed.
It does not matter if you can't see that finding the comment line button took 5 minutes. It did for me and I have been using VS since 2003. We are not referring to bugs here rather design choices by Microsoft. If you like the new design great, if you don't care then fine but don't think that it does not have an impact on other because it does on me.
Apple are losing money? Really? $9.5bn profit last quarter on a turn over of $43.6bn. While this is a fall in profits don't think that Apple will go away anytime soon. One of my friends recently started an XCode project and is loving it so again that is entirely subjective, just like our complaints on the VS2012 UI.
@ Phil, Posting my real name makes very little difference, by all means call me Mhil Purray, it wont change anything. Also VS2012 is no longer in beta, so that cant be an excuse, there were a lot of errors and bugs in beta and it would crash often, surely you don't expect people to comment on them now still? I also cant see why it would take 5 mins to find Comment Line.
I doubt the design choice of VS is affecting mobile computing either, Apple are losing money and are showing worrying signs and XCode despite being awful has a lot of UI changing options.
Surely if cap menus give you eyestrain then constants and enums do too?
Phil Murray commented
@Anon, The problems with the UI are not simply down to the colour schemas or the uppercase menu items they are around usability.
For instance, on installing the Beta version it took me five minutes to figure out where the line comment button was. The glyph's are not only ugly but for a while decreased my productivity.
Don't forget that in the beta version there were no colour theme's, the glyphs were all different and everything was unfamiliar. Another case of "someone moved my cheese".
I hate the shouty capitalised menus but do they affect my productivity, no.
Microsoft has some issues at the moment in trying to get market share in developed area such as mobile computing but annoying the development community id not a was to do this.
I always go back to the fact that I have to have Visual Studio 08, 10 and 12 installed to cover different platforms within my company rather than being able to develop everything from one IDE.
It all comes down to one thing. If it affects my productivity and causes me eye strain then I'm not going to like it.
Nice you see you publishing you real name in your posts as well. Ahem, Anon.
I really wish I could downvote all the threads / posts about menu headers being in caps. Are you people seriously unable to work due to all caps menus? Wow!
I would hate to be working with you guys on a project, "ewww there is a dead fly in the corner of the desk, that's it im refusing to work until this is fixed, it is obviously affecting my work, marriage and health".
It is just caps and you people are freaking out and being all dramatic like MS decided to discontinue VS
No MS, your time is better spent on other things, if someone gets upset by caps then clearly they will be getting upset by a million and one other things and if people are distracted by the caps then they have attention issues, they aren't hypnotic and if you are working you wont even notice the caps.
Please, make us concentrate on benefits of Visual Studio, not its ugly uppercase interface.
This is not a tablet. This is not a tool for computer newbs. This is not running on a phone. Stop yelling at me in all caps. Do you write you code in all caps? It is ****** to read and provides less "shape" to help quickly scan for and finding what I'm looking for.
Generally, I think the C++/MFC project settings/ UI controls / classes need some reviewing...
WPF projects don't have so many problems (or not at all).
Why don't you care about native C++ too???
I hope you fixed this:
I'm getting it in a Adobe After Effects Plugin project and it is really annoying.
"developers care more about an IDE's interface ( which structurally is not that different to 2010) then the technology running the system"
We've reached a point in the technological level of our tools and processes that the vast majority of coding problems have been solved. Any more we are simply implementing already proven solutions to common problems. Quite frankly, the extensions to the core .net languages present in 4.5 are unnecessary and don't appreciably move the product forward. Because of this, VS2012 is actually an unnecessary upgrade.
This particular item, along with the color issue, should be a bellwether to MS that changing the interface for it's own sake is no longer an acceptable approach for a new version. There are a tremendous number of people whose livelihood is interrupted whenever they are forced to deal with a new UI. This might seem trivial to you, but when you have grown accustomed to a way of working over a period of years, any change to that must have an honest purpose or it is met with severe resistance.
Moving from Camel Case to ALL CAPS is a change that has no bearing on how we work with the machine and as such is simply a change for it's own purpose. This isn't acceptable.
Looking beyond the desktop, Apples UI on the iPhone was an actual revolution. The previous mechanisms for working with phones were incredibly difficult. The iPhone not only changed how people interact with phones but via the other software (iTunes) actually made it useful. Simple example: no more pressing "5" three times to get an L to display.
Contrast that with MS's UI change. We still use a keyboard and mouse. We still go through various layers of menus to get to the features we want. In short, the UI change didn't actually change how we interact with the machine; instead it just reorganized things into a slightly different view. This is no longer acceptable.
What you are witnessing is some of the blowback from a very bad idea. Now, just imagine if Win8 gets rolled out across a medium or large sized organization. IT departments will be skewered.
The interface is important because we are interacting with it every day. We are making useful contributions all the time. Lately, Microsoft seems to be hellbent to prove its own customers wrong.
Why is the setting controlling the casing hidden in the registry? Why is it not accessible via Extras->Options?
Can I vote this down , and vote up the pedantic uselessness of this post. This current implementation of caps is in line with current linguistic constructs. For all of you who keep incorrectly using personification to describe the menu as shouting to them, please bare in mind that these items are headers and not sentences.
"All caps is usually used for emphasis"
Please ppl get on with coding and actual development issues in the new framework. This is just plain stupid, if you want to be all **** about letters go become a hipster designer somewhere and talk about Helvetica all day while trying to figure out if xcode is an IDE or a glorified mp3 player.
"they screwed up everything on this release. i am boycotting VS2012 until they get some sense."
seriously this is madness .. this is either serious trolling or I have entered into some weird twilight zone where developers care more about an IDE's interface ( which structurally is not that different to 2010) then the technology running the system. All of you designers / developers please go download snoop => look at the code building this IDE and make some useful contributions to the development platform. You all making yourselves look like angry little n00bs.
eggs, a real possibility ;}
Rick C. Hodgin commented
I am guessing the developers who make Visual Studio at Microsoft are having cases of paper towel rolls sent to their cubicles -- so they can remove all the egg from their faces, something which (along with the Metro design team) is undoubtedly a 2+ hour affair each day. :-(
The option for Proper Case has already been completed - see here:
So we got the the theme editor and the caps issue resolved. The next hurdle is to get the VS2010 icons back. It'd also be nice to get back the original VS2010 chrome and have it respect the Windows theme setting like Aero.
Janie Pumphrey commented
You can change the capitalization back to normal with these steps:
1. Close Visual Studio
2. Launch regedit and navigate to
3. Create a DWORD value named SuppressUppercaseConversion with value 1.
Tim Eicher commented
I don't think the caps would bug me so much except that it contradicts the CamelCase naming conventions used *everywhere* else.
Also, what is gained by switching to caps? I understand the need to make changes for improvements, but I don't what the gains are by using all caps.
It is as if your menu is shouting at you. How rude!
Worst idea ever... bad, bad design... what are they thinking?
Janie Pumphrey commented
People who use Visual Studio 8 hours a day already know where the menu is...it's at the top of the screen (duh). It's distracting and unnecessary to emphasize the main menu.
But if you really feel the need to emphasize it anyway, just use a slightly different background color instead of all caps.Text in all caps looks stressful and urgent. Developers have enough deadline stress already...don't add this artificial "false alarm" stress on top of it.