After installing this plugin i wasn't able to load any solution, bunch of VS "this contract couldn't be loaded" errors were appearing. I couldn't even close VS, I had to use task manager end process! Only after uninstalling extension i was able to open solution again.
Great extension, I love it.
The only thing I would suggest is if you can make it so when the mouse cursor is close to where the main menu is it will un-hide it. That way you can either use the hotkeys or use the mouse to show it.
I Think it would be really nice to be able to enable/disable the hiding of the main menu based on the mode of Visual Studio. For example I would like the menu to be visible for normal and debug mode but hidden when switching to full screen mode.
This may not be a common problem but it's a bug nonetheless:
* Gets the latest VS2010 bits
* Use the `C#` environment profile
* Assign `[SHIFT]+[ALT]+[F]` to `Project.NewFolder` in Keyboard shortcut options dialog.
* Install the Hide Menu extension and restart VS2010
* Load any project and click inside the Solution Explorer
* Hit `[SHIFT]+[ALT]+[F]`.
Expected: New folder is created.
What happens: The menu is shown.
Presumably because Hide Menu hi-jacked the shortcut or the focus somehow left the Solution Explorer before it has received the key combination.
Anyway, please fix it if you can... nice extension :)
Always love to maximize screen real estate.
But I have lots of custom shortcuts and this is a deal breaker. ([SHIFT]+[ALT]+[C] is also the default shortcut for `new class` in default C# profile)
That's interesting, I was unable to reproduce that behavior on my machine (with VS 2010 RTM). Is it at all possible your Shift key was stuck? Is it possible there are other extensions that could interfere with keyboard input? I even tried mapping Alt F to Project.NewFolder, and Alt F only creates a new folder without showing the menu.
I do see this behavior when the command is disabled (for example, if a code file is focused instead of the Solution Explorer), but that's expected behavior.
If this does repro, though, I don't believe it is the extension's fault, as the extension doesn't hijack any keyboard input. The extension works by making the Menu's Height 0 when the Menu doesn't have focus, and adds GotKeyboardFocus and LostKeyboardFocus event handlers to the Menu. When the menu gets focus, the fixed height is cleared. When the menu loses focus, the Height is set back to 0. Everything else (including all keyboard input) works as it would if the extension weren't installed.