5 ms·

menu still shouting

by r4vik 13y ago

menu still shouting

mikevm 13y ago
YOU DON'T GET IT, MAN. ALL-CAPS INCREASES VISIBILITY. DO YOU NOTICE HOW VISIBLE MY COMMENT IS?
- OrsenPike 13y ago
  Out of all of the changes they made the all caps menu is probably the most stupid in the history of Visual Studio. Thank god for http://blogs.msdn.com/b/zainnab/archive/2012/06/14/turn-off-the-uppercase-menu-in-visual-studio-2012.aspx http://blogs.msdn.com/b/zainnab/archive/2012/06/14/turn-off-...
mischanix 13y ago
I don't mind it. It's not like it's high-contrast, large font, or bold, it just serves as a heading for the menus they show without making the font large or bold. It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements.
- whaevr 13y ago
  >It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements. I feel your paIEnumerable
- acqq 13y ago
  > intellisense randomly breaking and putting a red line underneath half your statements There's a reasonably simple solution with which you can solve the red line problem, if you're talking about the C and C++ projects: http://connect.microsoft.com/VisualStudio/feedback/details/533605/stdafx-h-cant-be-parsed-with-intellisense-squiggles-mechanism http://connect.microsoft.com/VisualStudio/feedback/details/5... "Posted by JoeWoodbury on 25/02/2010 at 10:16 (...) The solution is to add the location of the stdafx.h file to the include path list. This is often a matter of simply putting a dot comma (.,) as the very first item in a projects include list."
  - mischanix 13y ago
    It happens regardless of precompiled headers, so I don't think that's the issue. I do think it's an include problem, but I don't know why.
    - acqq 13y ago
      It's precompiled headers and it can be proved: If you would try to turn off precompiled headers in your project and rebuild it, the compilation would fail in all the files in which you see the red lines. It's because your project has subfolders and the files in the subfolders reach stdafx only by accident of having the "use precompiled headers" turned on. So once you fix the include path, and that you can do on the project level, your project will compile independently of "use precompiled headers" settings and the intellisense would work too. I know from experience, I fixed the big projects on which I worked. EDIT v2: Looking at the project you cited in the reply of this message and the file: http://code.google.com/p/freetype-gl/source/browse/trunk/demo-font.c http://code.google.com/p/freetype-gl/source/browse/trunk/dem... on the computer on which I don't have VS, I still have an idea what the reason for such errors are: the project authors use something like: #elif defined(_WIN32) || defined(_WIN64) Now think about it: when intellisense parses the file, can it assume you're building a 32-bit version? No. Can it assume you're building a 64-bit version? No. So intellisense doesn't use the header inside that elif at all. Setting defines in the project can fix that.
      - mischanix 13y ago
        I'm not using PCH in the most recent example. I've been playing with this project: http://code.google.com/p/freetype-gl/ http://code.google.com/p/freetype-gl/ , so it includes Freetype, GLUT (using freeglut), and opengl stuff. Builds fine, intellisense lines everywhere.
      - mischanix 13y ago
        That's actually not it, but that idea helped me to find the issue. L52-56, this Freetype preprocessor magic defeats Intellisense https://code.google.com/p/freetype-gl/source/browse/trunk/texture-font.c#52 https://code.google.com/p/freetype-gl/source/browse/trunk/te... I feel silly for never mousing over the three characters at line 62 where Intellisense describes the problem it's having.
GravityWell 13y ago
I personally don't mind the menu caps, but I do find the way they are forcing their design choices on everyone somewhat antagonistic, and generally not smart. The same issue happened with their forced grey or white color schemes. It's not hard to give users the option to switch things like this to suit their preference. Yet MS has deliberately not provided any way to adjust these settings, and this gives users something to rant about, and rightly so. Really not a smart move in my view.
- jlewicki 13y ago
  You can indeed edit the color scheme. http://visualstudiogallery.msdn.microsoft.com/366ad100-0003-4c9a-81a8-337d4e7ace05 http://visualstudiogallery.msdn.microsoft.com/366ad100-0003-...
  - profquail 13y ago
    I use this extension -- it comes with a Blue theme which provides a color scheme that's reasonably close to VS2010 (for those that prefer it).
    - OrsenPike 13y ago
      FYI the blue theme is included as part of Update 2 for VS2012. It looks much nicer than the light and dark themes that 2012 has by default.
  - GravityWell 13y ago
    You can edit the scheme after hunting down and installing an extension which was not available at the initial release. The same could be said for the start menu on Win8. MS could have easily quieted the many loud voices by including options so the user can choose their own preferences.
Luyt 13y ago
This pisses me off, too. I really should patch the menu resource someday and change it to lowercase. I also don't understand that Microsoft violates its own HID guidelines; shouldn't they set a proper example?
- quasque 13y ago
  Easier method: http://stackoverflow.com/questions/10859173/how-to-disable-all-caps-menu-titles-in-visual-studio-2012-rc http://stackoverflow.com/questions/10859173/how-to-disable-a...
  - Luyt 13y ago
    Thank you very much for this tip.
scrabble 13y ago
I actually prefer the all-caps menu. I find that the letters being the same height improves readability for me. I wouldn't want to read a book that way though. It's similar to making notes by hand, I'll generally use all-caps when doing so.

menu still shouting

by r4vik 13y ago

menu still shouting

mikevm 13y ago

YOU DON'T GET IT, MAN. ALL-CAPS INCREASES VISIBILITY. DO YOU NOTICE HOW VISIBLE MY COMMENT IS?

OrsenPike 13y ago
Out of all of the changes they made the all caps menu is probably the most stupid in the history of Visual Studio. Thank god for http://blogs.msdn.com/b/zainnab/archive/2012/06/14/turn-off-the-uppercase-menu-in-visual-studio-2012.aspx http://blogs.msdn.com/b/zainnab/archive/2012/06/14/turn-off-...

mischanix 13y ago

I don't mind it. It's not like it's high-contrast, large font, or bold, it just serves as a heading for the menus they show without making the font large or bold. It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements.

whaevr 13y ago
>It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements. I feel your paIEnumerable
acqq 13y ago
> intellisense randomly breaking and putting a red line underneath half your statements There's a reasonably simple solution with which you can solve the red line problem, if you're talking about the C and C++ projects: http://connect.microsoft.com/VisualStudio/feedback/details/533605/stdafx-h-cant-be-parsed-with-intellisense-squiggles-mechanism http://connect.microsoft.com/VisualStudio/feedback/details/5... "Posted by JoeWoodbury on 25/02/2010 at 10:16 (...) The solution is to add the location of the stdafx.h file to the include path list. This is often a matter of simply putting a dot comma (.,) as the very first item in a projects include list."
- mischanix 13y ago
  It happens regardless of precompiled headers, so I don't think that's the issue. I do think it's an include problem, but I don't know why.
  - acqq 13y ago
    It's precompiled headers and it can be proved: If you would try to turn off precompiled headers in your project and rebuild it, the compilation would fail in all the files in which you see the red lines. It's because your project has subfolders and the files in the subfolders reach stdafx only by accident of having the "use precompiled headers" turned on. So once you fix the include path, and that you can do on the project level, your project will compile independently of "use precompiled headers" settings and the intellisense would work too. I know from experience, I fixed the big projects on which I worked. EDIT v2: Looking at the project you cited in the reply of this message and the file: http://code.google.com/p/freetype-gl/source/browse/trunk/demo-font.c http://code.google.com/p/freetype-gl/source/browse/trunk/dem... on the computer on which I don't have VS, I still have an idea what the reason for such errors are: the project authors use something like: #elif defined(_WIN32) || defined(_WIN64) Now think about it: when intellisense parses the file, can it assume you're building a 32-bit version? No. Can it assume you're building a 64-bit version? No. So intellisense doesn't use the header inside that elif at all. Setting defines in the project can fix that.
    - mischanix 13y ago
      I'm not using PCH in the most recent example. I've been playing with this project: http://code.google.com/p/freetype-gl/ http://code.google.com/p/freetype-gl/ , so it includes Freetype, GLUT (using freeglut), and opengl stuff. Builds fine, intellisense lines everywhere.
    - mischanix 13y ago
      That's actually not it, but that idea helped me to find the issue. L52-56, this Freetype preprocessor magic defeats Intellisense https://code.google.com/p/freetype-gl/source/browse/trunk/texture-font.c#52 https://code.google.com/p/freetype-gl/source/browse/trunk/te... I feel silly for never mousing over the three characters at line 62 where Intellisense describes the problem it's having.

GravityWell 13y ago

I personally don't mind the menu caps, but I do find the way they are forcing their design choices on everyone somewhat antagonistic, and generally not smart. The same issue happened with their forced grey or white color schemes. It's not hard to give users the option to switch things like this to suit their preference. Yet MS has deliberately not provided any way to adjust these settings, and this gives users something to rant about, and rightly so. Really not a smart move in my view.

jlewicki 13y ago
You can indeed edit the color scheme. http://visualstudiogallery.msdn.microsoft.com/366ad100-0003-4c9a-81a8-337d4e7ace05 http://visualstudiogallery.msdn.microsoft.com/366ad100-0003-...
- profquail 13y ago
  I use this extension -- it comes with a Blue theme which provides a color scheme that's reasonably close to VS2010 (for those that prefer it).
  - OrsenPike 13y ago
    FYI the blue theme is included as part of Update 2 for VS2012. It looks much nicer than the light and dark themes that 2012 has by default.
- GravityWell 13y ago
  You can edit the scheme after hunting down and installing an extension which was not available at the initial release. The same could be said for the start menu on Win8. MS could have easily quieted the many loud voices by including options so the user can choose their own preferences.

Luyt 13y ago

This pisses me off, too. I really should patch the menu resource someday and change it to lowercase. I also don't understand that Microsoft violates its own HID guidelines; shouldn't they set a proper example?

quasque 13y ago
Easier method: http://stackoverflow.com/questions/10859173/how-to-disable-all-caps-menu-titles-in-visual-studio-2012-rc http://stackoverflow.com/questions/10859173/how-to-disable-a...
- Luyt 13y ago
  Thank you very much for this tip.

scrabble 13y ago

I actually prefer the all-caps menu. I find that the letters being the same height improves readability for me. I wouldn't want to read a book that way though. It's similar to making notes by hand, I'll generally use all-caps when doing so.