---- some.h

class Some  < cursor caret in this line
{
   void member1();
   void member2()
   {
     // do something 2
   }
}

---- some.cpp

void Some::member1()
{
   // do something 1
}

//#VAssistX_Clipboard:entity=class
//#VAssistX_source:source=some.h
class Some
{
   void member1();
   void member2()
   {
     // do something
   }
}
//#VAssistX_source:source=some.cpp
void Some::member1()
{
   // do something 1
}

//#VAssistX_Clipboard:entity=member
//#VAssistX_source:source=some.h
class VATemplate
   void member1();
   void member2()
   {
     // do something 2
   }
....

quote:

---

Originally posted by feline

Simply looking at the ability to delete a class member, we are considering adding this as a refactoring command:

case=1101

---

quote:

---

The broader idea here, I am not quite sure what I think about it to be honest. This is a very appealing solution to moving a class from one file to another. The first question is simply how often does this need to happen? In my personal experience it is something I very rarely do.

I do sometimes copy a class, and use it as a template for a new class, but when doing this I normally only want the header file content, since I will be making new function implementations.

VA Outline helps, since you can quickly and easily select and copy things from the outline. Of course this only copies from a single file at a time.

---

quote:

---

Originally posted by feline


I have asked internally about this. There is a lot to like here, I am just not quite sure about some of the implications for modifying multiple files in one go.

---

quote:

---

Dans, modifying multiple files at once is "harder" in VC6, due to how the IDE and Undo work. This is one factor to consider. A second factor is modifying multiple files in one go makes any problems / mistakes by VA worse, and can break more code more quickly.

---

quote:

---

I am not saying it cannot or should not be done, but it needs to be done carefully

---

quote:

---

Originally posted by hotzenplotz

I like the clipboard idea.
And i think it wouldn't even be necessary to use a special shortcut for pasting. Clipboard is multi-format, so VAX could use a special "VAX-text" type, and only fall back to plain text if the application can't deal with VAX' special type (like when pasting the clipboard in notepad).
Another way would be to include something like a special GUID in the "//#VAssistX_Clipboard" header - that should make it reasonable safe to just process anything that contains that GUID as a "special VAX paste".

---

quote:

---

I'm not sure how helpful this feature would be in general, but I totally like the clipboard idea. It's so MacGyver :)

---