| T O P I C R E V I E W |
| hajokirchhoff |
Posted - Mar 13 2008 : 04:05:13 AM
Hello, I'd love to get some help from my VAssist plugin when I want to split source files.
These features would be wonderful to have:
1. move method/class to existing/new source file
I select a class identifier and choose 'move/extract'. VA asks me for a file name, either existing or new and then moves all code belonging to this class into a new .h/.cpp pair.
This would help me in situations where I have two or more classes inside a .h/.cpp pair and what to clean up the code.
2. Enhance the VA Outline window, so that
a) I can have multiple Outlines open
b) drag between Outline windows.
These would be great.
Oh, and when I move a class, automatic generation of appropriate #includes would be nice. Even if all VA did was clone the original .h/.cpp file until the first non #include would be helpful.
Thanks
Hajo |
| 2 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Jan 27 2009 : 10:26:12 PM
case=226 is implemented in build 1715
Hover over an unrecognized symbol and choose "Add include xxxx" from the refactoring context menu.
 |
| feline |
Posted - Mar 13 2008 : 2:33:53 PM
We have no plans to create new files, or add files to the solution. Firstly there is no general rule for where files are located on the hard drive, and secondly VA would have no idea which project and folder inside the project to place the new files into.
To move the code I would simply select the items you want to move in VA Outline, cut them, and then paste them into the new file.
We are considering a VA command to add missing #include statements to a file:
case=226 |
|
|
