IDE shortcuts
-
Has anyone noticed how much you need to use the mouse in the new IDE (compared to version 6)? If you're like me, you prefer using keyboard shortcuts, however I must say I find it very frustrating when I need to close x number of toolbar windows. Under version 6, you simply pressed 'esc' to close any active toolbar(s) and return focus to the main editor. I've tried playing with the customisable shortcut keys and the auto-hide features, but I still find it slow and clunky. I know I can close 'active' toolbars by 'shift-esc', however before they can be closed they first need activating ('shift-ctrl-o' for output, 'shift-ctrl-a' for tasks, etc, etc). In the end I'm going back to my mouse (too many shortcut keys to remember!). Does anyone share my frustrations, or am I missing something? Is there a way of making IDE perform the same as version 6 (I fear change! ;)) Alan
-
Has anyone noticed how much you need to use the mouse in the new IDE (compared to version 6)? If you're like me, you prefer using keyboard shortcuts, however I must say I find it very frustrating when I need to close x number of toolbar windows. Under version 6, you simply pressed 'esc' to close any active toolbar(s) and return focus to the main editor. I've tried playing with the customisable shortcut keys and the auto-hide features, but I still find it slow and clunky. I know I can close 'active' toolbars by 'shift-esc', however before they can be closed they first need activating ('shift-ctrl-o' for output, 'shift-ctrl-a' for tasks, etc, etc). In the end I'm going back to my mouse (too many shortcut keys to remember!). Does anyone share my frustrations, or am I missing something? Is there a way of making IDE perform the same as version 6 (I fear change! ;)) Alan
I have simmilar problems using the .NET IDE as you have, although htere will always be changes in life, I personally feel that these changes prevent me from working as effective as it could be. By the way in VS6 we hat F4 to move from one compiler error to the next one. In the new IDE F4 highlight the properties window. Any idea How I can move to the next compiler error without using the mouse? :mad: :mad: Rainer
-
I have simmilar problems using the .NET IDE as you have, although htere will always be changes in life, I personally feel that these changes prevent me from working as effective as it could be. By the way in VS6 we hat F4 to move from one compiler error to the next one. In the new IDE F4 highlight the properties window. Any idea How I can move to the next compiler error without using the mouse? :mad: :mad: Rainer
F8. The miserable !#@@!%@$'s changed every friggin' key assignment in the thing. Gary R. Wheeler
-
Has anyone noticed how much you need to use the mouse in the new IDE (compared to version 6)? If you're like me, you prefer using keyboard shortcuts, however I must say I find it very frustrating when I need to close x number of toolbar windows. Under version 6, you simply pressed 'esc' to close any active toolbar(s) and return focus to the main editor. I've tried playing with the customisable shortcut keys and the auto-hide features, but I still find it slow and clunky. I know I can close 'active' toolbars by 'shift-esc', however before they can be closed they first need activating ('shift-ctrl-o' for output, 'shift-ctrl-a' for tasks, etc, etc). In the end I'm going back to my mouse (too many shortcut keys to remember!). Does anyone share my frustrations, or am I missing something? Is there a way of making IDE perform the same as version 6 (I fear change! ;)) Alan
When I first heard back in 1998 that microsoft were going to produce a combined VB-style IDE (i.e., an evolution of Visual Interdev - which originally came from the VB IDE code base) for all the languages I expected that subsuming the functionality of the excellent VC++ Developer Studio IDE would be problematic. Sure enough, most complaints about the IDE have come from VC++ guys. For example see the Microsoft .NET newsgroups. Someone from the MS VC++ compiler team said that the IDE is likely to be significantly improved in the next version to address VC++ issues. I've posted an article on the site showing how to help out a bit on tool window management using a combination of command aliases and macros. It's not perfect but it cuts down a bit on the mouse. You might like to give it a try. http://www.codeproject.com/macro/vstogglewindow.asp I guess that between now and the next release the Add-In gurus (I'm not one of them!) will churn out some helpful IDE utilities. Joshua Jensen's Workspace Whizz for VS.NET is in Beta, for example. Kevin