| Author |
 Topic  |
|
|
silvermace
New Member
New Zealand
3 Posts |
 Posted - Jun 05 2009 : 03:12:52 AM
|
Eclipse has this ability for JDT (Java)
hitting Ctrl+Shift+O found all the unknown classes in the current file and automatically added the "most likely correct" import statement to the top of the file, extremely handy.
I see that VAX/VS can suggest these for individual occurences, but often when I paste in code or move code from one file to another, I have to go through one by one and fire this command via mouse, and I, along with many others, am more of a "keyboarder"
What's the likely hood of getting this feature in? I'd think it was pretty straight forward seeing the detection/resolution ability is already there for single instances.. just need to automate it a bit..
-Danu |
|
|
feline
Whole Tomato Software
United Kingdom
19249 Posts |
Posted - Jun 05 2009 : 12:05:21 PM
|
First the easy answer, you can trigger this command via the keyboard, no need to use the mouse. It is listed in the IDE VAssistX menu, and in the Shift + Right click menu, both of which can be accessed via the mouse.
Or you can just bind a keyboard shortcut to the command VAssistX.RefactorAddInclude
The idea of VA adding all of the missing include statements in one go is an interesting one, and I have put in a feature request for this:
case=27923 |
zen is the art of being at one with the two'ness |
 |
|
|
silvermace
New Member
New Zealand
3 Posts |
Posted - Jun 06 2009 : 02:17:53 AM
|
Thanks :)
An interesting variation of this feature was with IntelliJ 7 where pasting in any code brough up a dialog box with a list of dependencies that were going to be added to the import block... mind you IntelliJ is an IDE in a league of its own w.r.t to refactoring...
Thanks again,
-Danu |
|
|
|
feline
Whole Tomato Software
United Kingdom
19249 Posts |
Posted - Jun 08 2009 : 11:42:03 AM
|
Java is going to be a lot easier to refactor, you don't have to worry about people doing "fun" things with #define statements.
I am not sure about having a dialog pop up every time you paste some code into a file. Personally I often copy / paste reference code, and then delete most of it, since I just wanted to check on the parameters, or error / return handling for a given function. So having all of the #include statements added for a piece of code I am about to delete suggested and inserted does not seem all that helpful. |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
Resolve All References For File
